Re: Multiple NOTIFY is ignored

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Multiple NOTIFY is ignored
Дата
Msg-id CAKFQuwZg9wZukLekpBDjH=Ju4OG05=oKDQMNPksEHWEjJCqMaw@mail.gmail.com
обсуждение исходный текст
Ответ на Multiple NOTIFY is ignored  (Markus Kolb <markus.kolb+postgres@tower-net.de>)
Ответы Re: Multiple NOTIFY is ignored  (Igor Neyman <ineyman@perceptron.com>)
Список pgsql-general
On Thu, Jul 28, 2016 at 10:29 AM, Markus Kolb <markus.kolb+postgres@tower-net.de> wrote:
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.

​"​
dblink executes a query (usually a SELECT, but it can be any SQL statement that returns rows) in a remote database.
​"​


​As defined in the dblink docs your query isn't supported - its doesn't return rows.  I don't know the interaction that makes the separate executions succeed by I'd advise simply bypassing the issue and doing:

WHERE {3} is
SELECT pg_notify('{2}','{UPDATE NOTIFY}), pg_notify('{3}','{DELETE NOTIFY}');

Not tested and I've never used NOTIFY but the select makes it return rows.

I'm not positive how execution order plays out here, you may want to try "VALUES()" instead of multiple columns.

David J.

В списке pgsql-general по дате отправления:

Предыдущее
От: Alex Ignatov
Дата:
Сообщение: Re: Uber migrated from Postgres to MySQL
Следующее
От: Igor Neyman
Дата:
Сообщение: Re: Uber migrated from Postgres to MySQL