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

Re: BUG #5720: Bug for PQescapeByteaConn (libpq)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Eiichi Nakamura <nakamura(at)nepsys(dot)ddo(dot)jp>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
Date: 2010-10-23 04:58:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> On 23/10/2010 1:11 AM, Tom Lane wrote:
>> Why do you expect that?  The parameter only controls the *server*'s
>> output, it is not suggested anywhere that it should have an effect
>> on clients.

> I'm not at all sure what the right answer is here. I just wanted to 
> raise reasons why the OP isn't necessarily unreasonable in expecting the 
> behaviour they describe.

The definition of the PQescape functions is that they produce strings
that will be acceptable to the server they're connected to.  The OP
apparently wishes some other definition, but he's failed to put forward
any argument at all why it should be changed.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Andres FreundDate: 2010-10-23 14:19:33
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
Previous:From: Craig RingerDate: 2010-10-23 04:46:31
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)

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