Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 86485B5DBE0 for ; Tue, 24 May 2011 22:56:41 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 96435-02 for ; Wed, 25 May 2011 01:56:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from www.postnewspapers.com.au (www.postnewspapers.com.au [173.230.139.50]) by mail.postgresql.org (Postfix) with ESMTP id 9C207B5D801 for ; Tue, 24 May 2011 22:56:34 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by www.postnewspapers.com.au (Postfix) with ESMTP id 1EAEF2D; Tue, 24 May 2011 21:56:35 -0400 (EDT) X-Virus-Scanned: amavisd-new at postnewspapers.com.au.com Received: from www.postnewspapers.com.au ([127.0.0.1]) by localhost (www.postnewspapers.com.au [127.0.0.1]) (amavisd-new, port 10024) with LMTP id z78gB5tZEnlI; Tue, 24 May 2011 21:56:34 -0400 (EDT) Received: from mail.postnewspapers.com.au (ppp171-128.static.internode.on.net [150.101.171.128]) by www.postnewspapers.com.au (Postfix) with ESMTP id 54E7C27; Tue, 24 May 2011 21:56:34 -0400 (EDT) Received: from [10.0.0.53] (wallace.localnet [10.0.0.53]) by mail.postnewspapers.com.au (Postfix) with ESMTP id 50811AE348; Wed, 25 May 2011 09:56:33 +0800 (WST) Message-ID: <4DDC61D1.70009@postnewspapers.com.au> Date: Wed, 25 May 2011 09:56:33 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: Jasmin Dizdarevic CC: pgsql-sql@postgresql.org Subject: Re: Which version of PostgreSQL should I use. References: <1614341677-1306219359-cardhu_decombobulator_blackberry.rim.net-1916432553-@b26.c13.bise7.blackberry> <4DDB54A6.9000006@postnewspapers.com.au> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201105/149 X-Sequence-Number: 35433 On 24/05/11 18:58, Jasmin Dizdarevic wrote: > Alright, I've misunderstood this issue. Do you have to escape bytea > columns during export or import? And how you would do this? Some database drivers and some apps don't understand the new hex output format for bytea columns. IIRC, the format change should ONLY affect how bytea values are sent from the server to the client using the standard text-based postgresql protocol. When using apps/drivers that aren't ready for the hex format yet, you must SET bytea_output TO 'escape'; This can be done at the postgresql.conf level (globally), by ALTERing the database the app uses, by ALTERing the user ID the app connects with, or by modifying the app so it knows to issue an explicit SET before doing any work with a connection. AFAIK there is no impact on dump/load, though you *could* see problems if you used an application's own dump/load feature rather than pg_dump and the app wasn't ready for the new bytea format. -- Craig Ringer