Skip site navigation (1) Skip section navigation (2)

Re: large object I/O seeing \\xxx encoding with v3 protocol

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Eric Marsden <emarsden(at)laas(dot)fr>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol
Date: 2004-08-13 14:10:06
Message-ID: 22987.1092406206@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Eric Marsden <emarsden(at)laas(dot)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

In response to

Responses

pgsql-interfaces by date

Next:From: Eric MarsdenDate: 2004-08-13 15:39:21
Subject: Re: large object I/O seeing \\xxx encoding with v3
Previous:From: Oliver ArchnerDate: 2004-08-13 12:40:24
Subject: Calling C++ function

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group