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 17:49:49
Message-ID: 25124.1092419389@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Eric Marsden <emarsden(at)laas(dot)fr> writes:
>   It seems to me that it would be more useful, and more consistent
>   with the way text is handled in the fe/be protocol, to use the
>   character encoding that was requested by the client (the equivalent
>   of PQsetClientEncoding) instead of this literal \xxx escaping.

Surely not.  This is bytea data we are talking about --- there is no
reason to suppose that encoding has anything to do with it.  If you
want client_encoding to take a hand, you should be storing data as text
not bytea.

			regards, tom lane

In response to

pgsql-interfaces by date

Next:From: Tom LaneDate: 2004-08-15 18:27:38
Subject: Re: Calling C++ function
Previous:From: Eric MarsdenDate: 2004-08-13 15:39:21
Subject: Re: large object I/O seeing \\xxx encoding with v3

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