From: Eric Marsden <emarsden@laas.fr>
To: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Subject: large object I/O seeing \\xxx encoding with v3 protocol
Date: Fri, 13 Aug 2004 14:38:07 +0200
Message-ID: <wzivffncixc.fsf@melbourne.laas.fr> (raw)
Hi,
When using the v3 fe/be protocol, data read and written to large
objects via the loread and lowrite functions seems to be \\xxx
encoded, as per literal escaping or data for the BYTEA type. For
instance, newlines written using lowrite() are later received as
\\012.
[I am seeing this with my own implementation of the fe/be protocol;
I'm not using libpq.]
I find this behaviour to be unfortunate, because it differs from the
v2 protocol behaviour, and because I don't see any reason to encode
the binary data in large objects. Was this change intentional?
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
Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol
In-Reply-To: <wzivffncixc.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