Re: Discussion on a LISTEN-ALL syntax

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Trey Boudreau <trey(at)treysoft(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Discussion on a LISTEN-ALL syntax
Date: 2024-12-20 21:57:34
Message-ID: CAKFQuwaOufzPaakBGTuLhk5+MY4MavaTFGp2RmirguMS+c+RAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 20, 2024 at 2:42 PM Trey Boudreau <trey(at)treysoft(dot)com> wrote:

> We could have a different set of keywords, like LISTEN_ALL/UNLISTEN_ALL
> that doesn’t interfere with the existing behavior.
>
>
I think we will need something along these lines. We've given * a meaning
in UNLISTEN * that doesn't match what this proposal wants to accomplish.

I suggested using monitor/unmonitor but I suppose any unquoted symbol or
keyword that is invalid as a channel name would work within the
Listen/Unlisten syntax.

Otherwise I mis-spoke in my previous design since regardless of whether
Listen * unregisters existing channels or not Unlisten * will remove
everything and leave the session back at nothing. In which case you might
as well just remove the redundant channel listeners.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2024-12-20 22:00:12 Re: Re: proposal: schema variables
Previous Message David G. Johnston 2024-12-20 21:49:11 Re: Discussion on a LISTEN-ALL syntax