Re: Warning about LISTEN names

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Warning about LISTEN names
Date: 2007-02-20 19:38:33
Message-ID: 45DB4E39.6020301@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane wrote:
> "Greg Sabino Mullane" <greg(at)turnstep(dot)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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-20 20:04:34 Re: Warning about LISTEN names
Previous Message Bruce Momjian 2007-02-20 18:48:12 Re: [BUGS] BUG #2942: information_schema.element_types: documentation error