Re: Listen / Notify - what to do when the queue is full
От | Tom Lane |
---|---|
Тема | Re: Listen / Notify - what to do when the queue is full |
Дата | |
Msg-id | 27162.1263216357@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Listen / Notify - what to do when the queue is full (Arnaud Betremieux <arnaud.betremieux@keyconsulting.fr>) |
Ответы |
Re: Listen / Notify - what to do when the queue is full
Re: Listen / Notify - what to do when the queue is full |
Список | pgsql-hackers |
Arnaud Betremieux <arnaud.betremieux@keyconsulting.fr> writes: > 3) My use case : NOTIFY channel 'pay'||'load' (actually NOTIFY > channel '<table_name>#'||OLD.id) > 4) Taken one step further : NOTIFY channel (SELECT payload FROM payloads > WHERE ...) > I'm working on a proof of concept patch to use Joachim's new notify > function to introduce case 3. I think this means going through the > planner and executor, so I might as well do case 4 as well. It would be a lot less work to introduce a function like send_notify() that could be invoked within a regular SELECT. Pushing a utility statement through the planner/executor code path will do enough violence to the system design that such a patch would probably be rejected out of hand. regards, tom lane
В списке pgsql-hackers по дате отправления: