Large object reads/writes undergoing \\xxx escaping

From: Eric Marsden <emarsden(at)laas(dot)fr>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Large object reads/writes undergoing \\xxx escaping
Date: 2004-08-11 14:00:53
Message-ID: wzivffpepuy.fsf@melbourne.laas.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

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/>

Browse pgsql-interfaces by date

  From Date Subject
Next Message Warren W. Gay VE3WWG 2004-08-13 04:16:03 "WHERE CURRENT OF" Support in libpq Someday?
Previous Message pgsql 2004-08-11 07:48:35 Type implemented in plpythonu crashes backend