From: Eric Marsden <emarsden@laas.fr>
To: pgsql-interfaces@postgresql.org
Subject: Large object reads/writes undergoing \\xxx escaping
Date: Wed, 11 Aug 2004 16:00:53 +0200
Message-ID: <wzivffpepuy.fsf@melbourne.laas.fr> (raw)
Hi,
With recent PostgreSQL versions, I/O on large objects (via the
internal functions loread and lowrite) suffers \\xxx escaping, as per
the BYTEA type. For instance, newlines in the data passed to lowrite
are later read via loread as \\012.
I find this to be annoying (I don't see any reason for large object
data to go through any encoding whatsoever), and it doesn't seem to be
documented. Is it the intended behaviour?
[I am not using libpq; I see this using my own fe/be protocol
implementation.]
--
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 reads/writes undergoing \\xxx escaping
In-Reply-To: <wzivffpepuy.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