Re: Restrictions of channel arg of pg_notofy
От | Axel Rau |
---|---|
Тема | Re: Restrictions of channel arg of pg_notofy |
Дата | |
Msg-id | AE68D1AC-EC94-4F35-9C2C-65A6923D79E5@Chaos1.DE обсуждение исходный текст |
Ответ на | Restrictions of channel arg of pg_notofy (Axel Rau <Axel.Rau@Chaos1.DE>) |
Ответы |
Re: Restrictions of channel arg of pg_notofy
|
Список | pgsql-sql |
More details:Am 28.04.2019 um 19:30 schrieb Axel Rau <Axel.Rau@Chaos1.DE>:This is my test case with constant string:Am 28.04.2019 um 19:02 schrieb Tom Lane <tgl@sss.pgh.pa.us>:Hard to tell when you haven't provided a complete example.CREATE OR REPLACE FUNCTION syslog.new_event_action() RETURNS triggerLANGUAGE plpgsqlAS $$BEGINRAISE WARNING 'syslog.new_event_action() called.';PERFORM pg_notify('INSERTED', '');RETURN NEW;END$$;The warning is being logged.In psql session 1, I run a LISTEN INSERTED;In psql session 2, I run my INSERT (getting one row inserted)In psql session 1, I run SELECT now(); do not get asyncronous notification.
pg_catalog in not in search_path.
Axel
---
PGP-Key:29E99DD6 ☀ computing @ chaos claudius
PGP-Key:29E99DD6 ☀ computing @ chaos claudius
В списке pgsql-sql по дате отправления: