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 10:10:06 -0400
Message-ID: <22987.1092406206@sss.pgh.pa.us> (raw)
In-Reply-To: <wzivffncixc.fsf@melbourne.laas.fr>
References: <wzivffncixc.fsf@melbourne.laas.fr>
Eric Marsden <emarsden@laas.fr> writes:
> 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.]
It sounds to me like you have asked for textual rather than binary
results from loread.
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: <22987.1092406206@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