From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | Filip Rembiałkowski <filip(dot)rembialkowski(at)gmail(dot)com> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: make NOTIFY list de-duplication optional |
Date: | 2016-02-09 20:09:56 |
Message-ID: | CAK3UJRE3wdNj0_qB-dgb+JAj3iXFNtjSf649o3hh45QtayxS8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 9, 2016 at 2:16 PM, Filip Rembiałkowski
<filip(dot)rembialkowski(at)gmail(dot)com> wrote:
> But then it becomes disputable if SQL syntax change makes sense.
>
> ---we had this,
> NOTIFY channel [ , payload ]
> ---and in this patch we have this
> NOTIFY [ ALL | DISTINCT ] channel [ , payload ]
> --- but maybe we should have this?
> NOTIFY channel [ , payload [ , mode ] ]
I think using ALL to mean "don't worry about de-duplication" could be
a bit confusing, especially as there was some interest recently in
supporting wildcard notifications:
http://www.postgresql.org/message-id/52693FC5.7070507@gmail.com
and conceivably we might want to support a way to notify all
listeners, i.e. NOTIFY * as proposed in that thread. If we ever
supported wildcard notifies, ALL may be easily confused to mean "all
channel names".
What about adopting the options-inside-parentheses format, the way
EXPLAIN does nowadays, something like:
NOTIFY (DEDUPLICATE FALSE, MODE IMMEDIATE) mychannel;
Josh
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-02-09 20:10:15 | Re: pgsql: postgres_fdw: Push down joins to remote servers. |
Previous Message | Robert Haas | 2016-02-09 20:05:14 | Re: Multi-tenancy with RLS |