Re: large object I/O seeing \\xxx encoding with v3 protocol - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: large object I/O seeing \\xxx encoding with v3 protocol
Date
Msg-id 25124.1092419389@sss.pgh.pa.us
Whole thread Raw
In response to Re: large object I/O seeing \\xxx encoding with v3  (Eric Marsden <emarsden@laas.fr>)
List pgsql-interfaces
Eric Marsden <emarsden@laas.fr> writes:
>   It seems to me that it would be more useful, and more consistent
>   with the way text is handled in the fe/be protocol, to use the
>   character encoding that was requested by the client (the equivalent
>   of PQsetClientEncoding) instead of this literal \xxx escaping.

Surely not.  This is bytea data we are talking about --- there is no
reason to suppose that encoding has anything to do with it.  If you
want client_encoding to take a hand, you should be storing data as text
not bytea.
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Eric Marsden
Date:
Subject: Re: large object I/O seeing \\xxx encoding with v3
Next
From: Oliver Archner
Date:
Subject: Calling C++ function