Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand
Date
Msg-id 2696.1581701459@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand
List pgsql-bugs
"David G. Johnston" <david.g.johnston@gmail.com> writes:
>> пт, 14 февр. 2020 г. в 20:36, Tom Lane <tgl@sss.pgh.pa.us>:
>>> Doesn't sound like a bug to me.  The sending backend will only
>>> send out notifications when it goes idle

>  Does a non-interactive psql session ever go idle mid-script?

Sure.  "idle" here means that the backend is done with the current
command from the client.  I think the OP's problem largely stems from
trying to do two transactions in one simple-query message, which is
an abuse of that feature to begin with.  (We've discussed taking away
the ability to do that altogether, and while I've resisted that on
backwards-compatibility grounds, it might well happen someday.)

            regards, tom lane



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand
Next
From: PG Bug reporting form
Date:
Subject: BUG #16259: Cannot Use "pg_ctl start -l logfile" on Clean Install on Windows Server 2012/2016