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

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

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Eiichi Nakamura <nakamura(at)nepsys(dot)ddo(dot)jp>
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
Date: 2010-10-23 14:19:33
Message-ID: 201010231619.35074.andres@anarazel.de (view raw or flat)
Thread:
Lists: pgsql-bugs
On Saturday 23 October 2010 06:46:31 Craig Ringer wrote:
> On 23/10/2010 1:11 AM, Tom Lane wrote:
> > "Eiichi Nakamura"<nakamura(at)nepsys(dot)ddo(dot)jp>  writes:
> >> For PostgreSQL 9.0.1, after changing server "bytea_output" parameter as
> >> "escape" in postgresql.conf file, it is expected that PQescapeByteaConn
> >> (libpq) returns "escape" format.
> > 
> > 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.
> 
> IMO it seems like a reasonable expectation on the face of it. The client
> can tell what bytea format the server wants, as it has a connection to
> the server and the ability to read the appropriate GUC. The whole point
> of the 'Conn' functions is that they're capable of being sensitive to
> the configuration of the current connection.
The GUC controlls the output - it doesnt control the allowed input. The switch 
on the client needs to get based on the version - which hopefully doesnt 
change in a single connection ;-)


Andres

In response to

Responses

pgsql-bugs by date

Next:From: Craig RingerDate: 2010-10-23 14:59:28
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
Previous:From: Tom LaneDate: 2010-10-23 04:58:01
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)

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