| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | RekGRpth <rekgrpth(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand |
| Date: | 2020-02-14 17:30:59 |
| Message-ID: | 2696.1581701459@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> пт, 14 февр. 2020 г. в 20:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-02-14 17:35:00 | BUG #16259: Cannot Use "pg_ctl start -l logfile" on Clean Install on Windows Server 2012/2016 |
| Previous Message | David G. Johnston | 2020-02-14 17:14:53 | Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand |