From: Eric Marsden <emarsden@laas.fr>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: large object I/O seeing \\xxx encoding with v3
Date: Fri, 13 Aug 2004 17:39:21 +0200
Message-ID: <wzir7qbcaja.fsf@melbourne.laas.fr> (raw)
In-Reply-To: <22987.1092406206@sss.pgh.pa.us>
References: <wzivffncixc.fsf@melbourne.laas.fr>
<22987.1092406206@sss.pgh.pa.us>
>>>>> "tl" == Tom Lane <tgl@sss.pgh.pa.us> writes:
ecm> When using the v3 fe/be protocol, data read and written to large
ecm> objects via the loread and lowrite functions seems to be \\xxx
ecm> encoded, as per literal escaping or data for the BYTEA type. For
ecm> instance, newlines written using lowrite() are later received as
ecm> \\012.
tl> It sounds to me like you have asked for textual rather than binary
tl> results from loread.
you're right; I am sending the type of the argument as 0, so it's text.
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.
Would be a backwards-incompatible change, though.
Thanks,
--
Eric Marsden <URL:http://www.laas.fr/~emarsden/;
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: emarsden@laas.fr, tgl@sss.pgh.pa.us
Subject: Re: large object I/O seeing \\xxx encoding with v3
In-Reply-To: <wzir7qbcaja.fsf@melbourne.laas.fr>
* 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