Re: LISTEN / NOTIFY enhancement request for Postgresql

From: Sev Zaslavsky <sevzas(at)gmail(dot)com>
To: Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: LISTEN / NOTIFY enhancement request for Postgresql
Date: 2013-11-18 14:15:39
Message-ID: 528A210B.7020004@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)momjian(dot)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
>
>
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhan Li 2013-11-18 14:28:17 Force optimizer to use hash/nl/merge join?
Previous Message Peter Eisentraut 2013-11-18 14:13:30 Re: additional json functionality