Re: LISTEN / NOTIFY enhancement request for Postgresql
От | Sev Zaslavsky |
---|---|
Тема | Re: LISTEN / NOTIFY enhancement request for Postgresql |
Дата | |
Msg-id | 528A210B.7020004@gmail.com обсуждение исходный текст |
Ответ на | Re: LISTEN / NOTIFY enhancement request for Postgresql (Pavel Golub <pavel@microolap.com>) |
Ответы |
Re: LISTEN / NOTIFY enhancement request for Postgresql
Re: LISTEN / NOTIFY enhancement request for Postgresql |
Список | pgsql-hackers |
Thank you all for considering my feature request. Dimitri's suggestion is a very good one - I feel it will accomplish the goal of allowing more granularity in the "Listen". We might also want to add a flag in postgresql.conf to disable this enhancement so that we don't break existing code. On 11/15/2013 8:19 AM, Pavel Golub wrote: > Hello, Dimitri. > > You wrote: > > DF> Bruce Momjian <bruce@momjian.us> writes: >>>> • is used to separate names in a path >>>> • * is used to match any name in a path >>>> • > is used to recursively match any destination starting from this name >>>> >>>> For example using the example above, these subscriptions are possible >>>> >>>> Subscription Meaning >>>> PRICE.> Any price for any product on any exchange >>>> PRICE.STOCK.> Any price for a stock on any exchange >>>> PRICE.STOCK.NASDAQ.* Any stock price on NASDAQ >>>> PRICE.STOCK.*.IBM Any IBM stock price on any exchange >>>> >>>> >>>> My request is to implement the same or similar feature in Postgresql. >>> This does seem useful and pretty easy to implement. Should we add a >>> TODO? > DF> I think we should consider the ltree syntax in that case, as documented > DF> in the following link: > > DF> http://www.postgresql.org/docs/9.3/interactive/ltree.html > > Great idea! Thanks for link. > > DF> Regards, > DF> -- > DF> Dimitri Fontaine > DF> http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support > > > > >
В списке pgsql-hackers по дате отправления: