Re: LISTEN/NOTIFY versus encoding conversion - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: LISTEN/NOTIFY versus encoding conversion
Date
Msg-id 1266269077.29919.6936.camel@jdavis
Whole thread Raw
In response to Re: LISTEN/NOTIFY versus encoding conversion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Listen / Notify - what to do when the queue is full
Next
From: Hans-Jürgen Schönig
Date:
Subject: one more index for pg_tablespace?