From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201010212129.o9LLTBl21612@momjian.us>
Subject: Re: Gripe: bytea_output default => data corruption
In-Reply-To: <AANLkTi=SH6s3FcsCf0quZm09-XgncTnQPR18-Z6GVqsU@mail.gmail.com>
To: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
Date: Thu, 21 Oct 2010 17:29:11 -0400 (EDT)
CC: ljb <ljb9832@pobox.com>, pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Rajesh Kumar Mallah wrote:
> Dear Griper!,
> 
> fortunately someone showed a easy 'fix'
> 
> ALTER DATABASE foo SET bytea_output='escape' ;

Yes, we mentioned that setting in the release notes too:

	E.2.3.5. Data Types
	
	    *
	
	      Allow bytea values to be written in hex notation (Peter
	Eisentraut)
	
	      The server parameter bytea_output controls whether hex or
	traditional format is used for bytea output. Libpq's PQescapeByteaConn()
	function automatically uses the hex format when connected to PostgreSQL
	9.0 or newer servers.
	
	      The new hex format will be directly compatible with more
	applications that use binary data, allowing them to store and retrieve
	it without extra conversion. It is also significantly faster to read and
	write than the traditional format. 

While the "Incompatibilities" section mentions only the first paragraph,
this remention lower down has even more details.  Not sure what else you
wanted us to do.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +