Re: NOTIFY does not work as expected
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Andrey <parihaaraka@gmail.com>, Pg Bugs <pgsql-bugs@postgresql.org>
Date: 2018-07-03T05:28:50Z
Lists: pgsql-bugs
Jeff Janes <jeff.janes@gmail.com> writes: > On Mon, Jul 2, 2018 at 4:33 PM, Andrey <parihaaraka@gmail.com> wrote: >> [ delayed receipt of notifications ] > I don't think this is a bug. I don't see that the docs promise one > behavior over the other, so it is really a dealer's choice. Also, I can't > reliably reproduce the reported 9.6.2 behavior on my own 9.6.2 server. FWIW, it looks like a bug to me. I don't have time to investigate further right now, though. It's also not at all clear whether the issue is in the server or libpq or psql ... regards, tom lane
Commits
-
Client-side fixes for delayed NOTIFY receipt.
- ecc59e31a81e 10.6 landed
- d30d27a52818 11.1 landed
- ac3be116a798 9.5.15 landed
- 4247db62522f 12.0 landed
- 34aad21cbf03 9.6.11 landed
-
Server-side fix for delayed NOTIFY and SIGTERM processing.
- f4941666afc6 9.5.15 landed
- cbab94077e12 9.6.11 landed
- 7aaeb7b45ac7 11.1 landed
- 3bdef6d21131 10.6 landed
- 2ddb9149d14d 12.0 landed
-
Introduce and use infrastructure for interrupt processing during client reads.
- 4f85fde8eb86 9.5.0 cited