Postgres Pro
Downloads
Home   >   mailing lists

Large object reads/writes undergoing \\xxx escaping - Mailing list pgsql-interfaces

From Eric Marsden
Subject Large object reads/writes undergoing \\xxx escaping
Date
Msg-id wzivffpepuy.fsf@melbourne.laas.fr
Whole thread Raw
List pgsql-interfaces
Tree view 
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 protocolimplementation.] 

-- 
Eric Marsden                          <URL:http://www.laas.fr/~emarsden/>

pgsql-interfaces by date:

Previous
From: Oliver Archner
Date:
Subject: Calling C++ function
Next
From: pgsql@groks.org
Date:
Subject: Type implemented in plpythonu crashes backend