Re: Multiple NOTIFY is ignored - Mailing list pgsql-general

From Tom Lane
Subject Re: Multiple NOTIFY is ignored
Date
Msg-id 19680.1469722549@sss.pgh.pa.us
Whole thread Raw
In response to Multiple NOTIFY is ignored  (Markus Kolb <markus.kolb+postgres@tower-net.de>)
List pgsql-general
Markus Kolb <markus.kolb+postgres@tower-net.de> writes:
> If I only do one
> SELECT dblink_connect('{0}', '{1}'); SELECT dblink('{2}', '{3}'); SELECT
> dblink_disconnect('{4}');
> where {3} is
> NOTIFY upd_pgm, '0|UPDATE|A|'; NOTIFY upd_pgm, '0|DELETE|A|'
> only the notify with UPDATE is recognized.

I can't duplicate this.

contrib_regression=# SELECT dblink_connect('myconn',connection_parameters());
 dblink_connect
----------------
 OK
(1 row)

contrib_regression=# select dblink('myconn', $$notify foo,'0|UPDATE|A|'; notify foo,'0|DELETE|A|'$$);
  dblink
----------
 (NOTIFY)
(1 row)

Over in another session that's done "LISTEN foo":

contrib_regression=# select 1;
 ?column?
----------
        1
(1 row)

Asynchronous notification "foo" with payload "0|UPDATE|A|" received from server process with PID 19442.
Asynchronous notification "foo" with payload "0|DELETE|A|" received from server process with PID 19442.

            regards, tom lane


pgsql-general by date:

Previous
From: thomas veymont
Date:
Subject: Re: low perfomances migrating from 9.3 to 9.5
Next
From: Moreno Andreo
Date:
Subject: Re: WAL directory size calculation