On Mon, 2010-02-15 at 13:53 -0500, Tom Lane wrote:
> You're assuming that the LISTEN was transmitted across the connection,
> and not for example executed by a pre-existing function.

Ok, good point.

> In practice, since encoding conversion failures could interfere with the
> results of almost any operation, it's not apparent to me why we should
> single out NOTIFY as being so fragile it has to have an ASCII-only
> restriction.

Ok, it sounds reasonable to lift the restriction.

Regards,
	Jeff Davis

In response to

• Re: LISTEN/NOTIFY versus encoding conversion at 2010-02-15 18:53:21 from Tom Lane

pgsql-hackers by date

Next:	From: Jeff Davis	Date: 2010-02-15 21:36:55
	Subject: Re: Listen / Notify - what to do when the queue is full
Previous:	From: Martijn van Oosterhout	Date: 2010-02-15 21:15:00
	Subject: Re: LISTEN/NOTIFY versus encoding conversion