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

From Tom Lane
Subject Re: large object I/O seeing \\xxx encoding with v3 protocol
Date
Msg-id 22987.1092406206@sss.pgh.pa.us
Whole thread Raw
In response to large object I/O seeing \\xxx encoding with v3 protocol  (Eric Marsden <emarsden@laas.fr>)
Responses Re: large object I/O seeing \\xxx encoding with v3
List pgsql-interfaces
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


pgsql-interfaces by date:

Previous
From: Eric Marsden
Date:
Subject: large object I/O seeing \\xxx encoding with v3 protocol
Next
From: Eric Marsden
Date:
Subject: Re: large object I/O seeing \\xxx encoding with v3