Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
Date
Msg-id CA+hUKGK=X5KUgejt3cxER2G6GE+8eU0fmSsgYMG4XjkP7-==DA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
After looking into that a bit more and rediscovering/re-remembering
all the previous threads about RelationTruncate()'s failures, which
d87251048a0f has made worse, I now think we should do one of two
things:

1.  Fix bug #18146[1].  Then this WaitIO() problem will be fixed as a
side-effect.  I posted a new patch over there.

2.  If somehow we can't agree on that critical section in back
branches (for example if we finish up deciding to do the big
re-engineering project for truncation where the buffer pool has new
states, ie fix in HEAD only), then at least wrap the truncation in
HOLD_INTERRUPTS() for releases 14-17.

[1] https://www.postgresql.org/message-id/flat/18146-04e908c662113ad5%40postgresql.org



pgsql-bugs by date:

Previous
From: "1165125080"
Date:
Subject: 回复: BUG #18437: The index scan result is more than the full scan result, and the primary key index has duplicate val
Next
From: PG Bug reporting form
Date:
Subject: BUG #18446: Postgres.exe crash observed while installing the application