From: Tom Lane <tgl@sss.pgh.pa.us>
To: Eric Marsden <emarsden@laas.fr>
Cc: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol
Date: Fri, 13 Aug 2004 13:49:49 -0400
Message-ID: <25124.1092419389@sss.pgh.pa.us> (raw)
In-Reply-To: <wzir7qbcaja.fsf@melbourne.laas.fr>
References: <wzivffncixc.fsf@melbourne.laas.fr>
<22987.1092406206@sss.pgh.pa.us>
<wzir7qbcaja.fsf@melbourne.laas.fr>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, emarsden@laas.fr
Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol
In-Reply-To: <25124.1092419389@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox