Skip site navigation (1) Skip section navigation (2)

Re: LISTEN/NOTIFY versus encoding conversion

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: LISTEN/NOTIFY versus encoding conversion
Date: 2010-02-15 21:24:37
Message-ID: 1266269077.29919.6936.camel@jdavis (view raw or flat)
Thread:
Lists: 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


In response to

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group