Re: pg_notify but no pg_listen?
От
A.M.
Тема
Re: pg_notify but no pg_listen?
Дата
Msg-id
12119DBE-223F-47A1-A896-84DA430DE5BA@themactionfaction.com
Ответ на
Re: pg_notify but no pg_listen? (Craig Ringer)
Список
Дерево обсуждения
pg_notify but no pg_listen? "A.M." <agentm@themactionfaction.com>
Re: pg_notify but no pg_listen? Bruce Momjian <bruce@momjian.us>
Re: pg_notify but no pg_listen? Craig Ringer <craig@postnewspapers.com.au>
Re: pg_notify but no pg_listen? "A.M." <agentm@themactionfaction.com>
Re: pg_notify but no pg_listen? Craig Ringer <craig@postnewspapers.com.au>
How about synchronous notifications? Lincoln Yeoh <lyeoh@pop.jaring.my>
Re: How about synchronous notifications? Tom Lane <tgl@sss.pgh.pa.us>
Re: How about synchronous notifications? Merlin Moncure <mmoncure@gmail.com>
Re: How about synchronous notifications? Vick Khera <vivek@khera.org>
On Aug 23, 2010, at 10:18 PM, Craig Ringer wrote: > On 08/24/2010 06:43 AM, Bruce Momjian wrote: >> A.M. wrote: >>> There is a new pg_notify function in pgsql 9.0 but no pg_listen >>> equivalent? Why? It sure would be handy to pass quoted strings... >> >> Notify sends the notify; there is no place to send a 'listen' payload. > > I assume what they want is the ability to filter notifications, so they only get notifications with a certain payload. > > Seems to me that in that case you should just be using different notify values (possibly using the two-argument form of pg_notify) so you can listen on different things depending on what you are interested in. Actually, my use case was for parameterized queries and pl functions where it's much easier to use quoted strings for the notification name as well as the payload- it would just be a convenience, really. Cheers, M
В списке pgsql-general по дате отправления