Fix UNLISTEN to fall out quickly if the current backend has never executed
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 13 Feb 2009 17:12:04 +0000 (17:12 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 13 Feb 2009 17:12:04 +0000 (17:12 +0000)
commit5d2a33cc53db4d1996c81ab09c879ab8e5f31acb
treeedafafe6fb25a6d54633be2de6859e0f4bcbcc59
parent9697aaab2fdebcaa1107bdf918c3fec8378b3b24
Fix UNLISTEN to fall out quickly if the current backend has never executed
any LISTEN command.  This is more important than it used to be because
DISCARD ALL invokes UNLISTEN.  Connection-pooled applications making heavy
use of DISCARD ALL were seeing significant contention for pg_listener,
as reported by Matteo Beccati.  It seems unlikely that clients using LISTEN
would use pooled connections, so this simple tweak seems sufficient,
especially since the pg_listener implementation is slated to go away soon
anyway.

Back-patch to 8.3, where DISCARD ALL was introduced.
src/backend/commands/async.c