Re: Re: proposal: make NOTIFY list de-duplication optional - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Re: proposal: make NOTIFY list de-duplication optional
Date
Msg-id CA+hUKGJh7C+r8wFtOMUoSu9kPOa87tsa2d5cA=0qT2oaay+EEA@mail.gmail.com
Whole thread Raw
In response to Re: Re: proposal: make NOTIFY list de-duplication optional  (Filip Rembiałkowski <filip.rembialkowski@gmail.com>)
Responses Re: Re: proposal: make NOTIFY list de-duplication optional
List pgsql-hackers
On Fri, Mar 8, 2019 at 1:37 PM Filip Rembiałkowski
<filip.rembialkowski@gmail.com> wrote:
> See attached patch... I'm ready to work on so it can get merged in the next CF.

Hi Filip,

Seen on Travis:

     async                        ... FAILED      126 ms

Looks like the new error isn't being raised for invalid send mode?
(What kind of error message is "?" anyway? :-))

 ERROR:  channel name too long
 -- Should fail. Invalid 3rd parameter
 NOTIFY notify_async2, 'test', 'invalid';
-ERROR:  ?
 NOTIFY notify_async2, 'test', true;
-ERROR:  ?
 --Should work. Valid NOTIFY/LISTEN/UNLISTEN commands
 NOTIFY notify_async2;
 NOTIFY notify_async2, '';

--
Thomas Munro
https://enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Should we increase the default vacuum_cost_limit?
Next
From: Tom Lane
Date:
Subject: Re: Should we increase the default vacuum_cost_limit?