Re: Discussion on a LISTEN-ALL syntax - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Discussion on a LISTEN-ALL syntax
Date
Msg-id 782541.1734755009@sss.pgh.pa.us
Whole thread Raw
In response to Re: Discussion on a LISTEN-ALL syntax  (Vik Fearing <vik@postgresfriends.org>)
Responses Re: Discussion on a LISTEN-ALL syntax
List pgsql-hackers
Vik Fearing <vik@postgresfriends.org> writes:
> Could I perhaps propose a sort of wildmat[1] syntax?
> The above sequence could be expressed simply as:
>      LISTEN *,!foo.*,foo.bar.*

That doesn't absolve you from having to say what happens if the
user then issues another "LISTEN zed" or "UNLISTEN foo.bar.baz"
command.  We can't break the existing behavior that "LISTEN foo"
followed by "LISTEN bar" results in listening to both channels.
So on the whole this seems like it just adds complexity without
removing any.  I'm inclined to limit things to one pattern per
LISTEN/UNLISTEN command, with more complex behaviors reached
by issuing a sequence of commands.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: Discussion on a LISTEN-ALL syntax
Next
From: "Andrey M. Borodin"
Date:
Subject: Re: Fix logging for invalid recovery timeline