Re: BUG #5720: Bug for PQescapeByteaConn (libpq) - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
Date
Msg-id 201010231619.35074.andres@anarazel.de
Whole thread Raw
In response to Re: BUG #5720: Bug for PQescapeByteaConn (libpq)  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
List 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@nepsys.ddo.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)
Next
From: Craig Ringer
Date:
Subject: Re: BUG #5720: Bug for PQescapeByteaConn (libpq)