Hello, Sev.
You wrote:
SZ Thank you all for considering my feature request.
SZ Dimitri's suggestion is a very good one - I feel it will accomplish the
SZ goal of allowing more granularity in the Listen.
SZ We might also want to add a flag in postgresql.conf to disable this
SZ enhancement so
On Mon, Nov 18, 2013 at 09:15:39AM -0500, Sev Zaslavsky wrote:
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
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.
Hello, Dimitri.
You wrote:
DF Bruce Momjian br...@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
On Thu, Oct 24, 2013 at 11:41:57AM -0400, Sev Zaslavsky wrote:
Here is an example implementation: http://activemq.apache.org/nms/
activemq-wildcards.html
• is used to separate names in a path
• * is used to match any name in a path
• is used to recursively match any destination
Bruce Momjian br...@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
Hi pgsql-hackers,
The LISTEN / NOTIFY feature (along with the pg_notify() function) is a
unique feature that differentiates Postgresql from nearly all other
relational database systems. With the exception of SQL Server, I know
of no other RDBMSs that allow a client to be asynchronously
