> On Tue, Dec 5, 2023 at 9:03 PM Tom Lane wrote:
> Why should we regard that as anything other than a bug in the
> ProcessUtility hook? A failed transaction should not send any
> notifies.
Fair point. That was also my initial assumption but I thought that the
transaction
state was not available
Anthonin Bonnefoy writes:
> This happens when a transaction block fails and a ProcessUtility hook
> sends a notification during the rollback command.
Why should we regard that as anything other than a bug in the
ProcessUtility hook? A failed transaction should not send any
notifies.
> Moving no
Hi,
I've encountered the following segfault:
#0: 0x000104e821a8 postgres`list_head(l=0x7f7f7f7f7f7f7f7f) at
pg_list.h:130:17
#1: 0x000104e81c9c postgres`PreCommit_Notify at async.c:932:16
#2: 0x000104dd02f8 postgres`CommitTransaction at xact.c:2236:2
#3: 0x000104dcfc24 postgres`Co
