]> granicus.if.org Git - postgresql/commit
Fix bogus when-to-deregister-from-listener-array logic.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 13 Feb 2013 17:48:05 +0000 (12:48 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 13 Feb 2013 17:48:05 +0000 (12:48 -0500)
commitcd89965aab34463252b9354bc1bf1bcf0339c102
tree257bcedd2cb19d2fa7b264d7ff7e69a69c53a79f
parentfdf9e21196a6f58c6021c967dc5776a16190f295
Fix bogus when-to-deregister-from-listener-array logic.

Since a backend adds itself to the global listener array during
Exec_ListenPreCommit, it's inappropriate for it to remove itself during
Exec_UnlistenCommit or Exec_UnlistenAllCommit --- that leads to failure
when committing a transaction that did UNLISTEN then LISTEN, since we end
up not registered though we should be.  (This leads to missing later
notifications, or to Assert failures in assert-enabled builds.)  Instead
deal with deregistering at the bottom of AtCommit_Notify, when we know the
final state of the listenChannels list.

Also, simplify the representation of registration status by replacing the
transient backendHasExecutedInitialListen flag with an amRegisteredListener
flag.

Per report from Greg Sabino Mullane.  Back-patch to 9.0, where the problem
was introduced during the LISTEN/NOTIFY rewrite.
src/backend/commands/async.c