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

Re: LISTEN/NOTIFY versus encoding conversion

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
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:15:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sun, Feb 14, 2010 at 03:15:30PM -0500, Tom Lane wrote:
> So the currently submitted patch is logically inconsistent.  If we
> enforce a character set restriction on the payload for fear of
> being unable to convert it to the destination client_encoding, then
> we should logically do the same for the condition name.  But then
> why not also restrict a lot of other things to pure ASCII?

AFAICS this essentially goes for "payload is a text string" and for
people who want "payload as binary" will have to do hex encoding or
some such. At least, I thought one of the reasons why it got limited
was because we couldn't decide.

Have a nice day,
Martijn van Oosterhout   <kleptog(at)svana(dot)org>
> Please line up in a tree and maintain the heap invariant while 
> boarding. Thank you for flying nlogn airlines.

In response to

pgsql-hackers by date

Next:From: Jeff DavisDate: 2010-02-15 21:24:37
Subject: Re: LISTEN/NOTIFY versus encoding conversion
Previous:From: Federico Di GregorioDate: 2010-02-15 20:41:21
Subject: Re: psycopg2 license changed

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