Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
We'll also need to store the database id along with the event name and
message, since pg_listener is per db rather than per cluster.
Well, that's an artifact of the historical implementation ... does
anyone want to argue that LISTEN should be cluster-wide given the
opportunity?
That would be a problem if you try to run multiple installations of an
application that uses NOTIFY/LISTEN in separate databases in a single
cluster. Applications would overhear each other. I'd consider that as a
bug, not a feature.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
