Postgres Pro
Downloads
Home   >   mailing lists

large object I/O seeing \\xxx encoding with v3 protocol - Mailing list pgsql-interfaces

From Eric Marsden
Subject large object I/O seeing \\xxx encoding with v3 protocol
Date
Msg-id wzivffncixc.fsf@melbourne.laas.fr
Whole thread Raw
Responses Re: large object I/O seeing \\xxx encoding with v3 protocol
List pgsql-interfaces
Tree view 
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/>

pgsql-interfaces by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: "WHERE CURRENT OF" Support in libpq Someday?
Next
From: Tom Lane
Date:
Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol