Re: Warning about LISTEN names - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: Warning about LISTEN names
Date
Msg-id 45DB4E39.6020301@dunslane.net
Whole thread Raw
In response to Re: Warning about LISTEN names  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Warning about LISTEN names  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> "Greg Sabino Mullane" <greg@turnstep.com> writes:
>
>> I'll save the full rant for my blog :), but wanted to submit this documentation
>> patch for this listen gotcha that's been bugging me for a while. I'd like
>> to see LISTEN and NOTIFY changed to use a simple text string, but until then,
>> I think we should probably warn about the chopping off of the left-hand part.
>>
>
> Let's change it to a plain ColId, so you get a syntax error if you try
> that.
>
>
>

Makes sense.

I'm still going to try to get notification payloads done for 8.3, which
will remove any requirement of catalog support and do it all in shared
memory.

Should we perhaps support a variant that allows a string as opposed to
an identifier as the name?

  LISTEN
'really_really_really_really_really_really_really_really_really_really_really_really_long_name'
;

Or is that just silly? ;-)

cheers

andrew


pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #2942: information_schema.element_types: documentation error
Next
From: Tom Lane
Date:
Subject: Re: Warning about LISTEN names