Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id A6EB2B5DBE7
	for <pgsql-sql-postgresql.org@mail.postgresql.org>;
	Tue, 24 May 2011 07:58:25 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 43532-06 for
	<pgsql-sql-postgresql.org@mail.postgresql.org>;
	Tue, 24 May 2011 10:58:18 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-yx0-f174.google.com (mail-yx0-f174.google.com
	[209.85.213.174])
	by mail.postgresql.org (Postfix) with ESMTP id BCDD5B5DBE8
	for <pgsql-sql@postgresql.org>; Tue, 24 May 2011 07:58:18 -0300 (ADT)
Received: by yxs7 with SMTP id 7so2503902yxs.19
	for <pgsql-sql@postgresql.org>; Tue, 24 May 2011 03:58:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type;
	bh=J1gobg0F+LfJ+Dm7x86MB3ClnP9QIca/+tTfsaSezzw=;
	b=VnfHxMBI9dYLcf+bsTQdMV1K11wfoikJI7AlVfsQRAGypQcoIZcftOJpPiVXqWI+7i
	yGDI0iE2SkpGuSCRu038N+O0RV+m+qgD5/ZwpYwVOpT1GbGxveVgOjEh7d1UWawyA2tq
	bgSGI2v8XijgcfFSFirLqkFMxm1u6CWMOvYLc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	b=vsNFenBYZHP9XsZE+0nt3WMVRAUz9ak0R6u+OO/nA1Rvl6ZrNl14PPad3f5Esri/wU
	g0cWLB6m1gbc5ZW+uFWQvx7A74gV/YRV3Oip404QAKOvgkPy34FEobwvnThc9xHylXwf
	BcIeh7LqZokZbtBlKrFpNafJrRIZ2/pszlEBI=
MIME-Version: 1.0
Received: by 10.236.154.70 with SMTP id g46mr4313833yhk.446.1306234698608;
	Tue, 24 May 2011 03:58:18 -0700 (PDT)
Received: by 10.236.110.129 with HTTP; Tue, 24 May 2011 03:58:18 -0700 (PDT)
In-Reply-To: <4DDB54A6.9000006@postnewspapers.com.au>
References: 
 <1614341677-1306219359-cardhu_decombobulator_blackberry.rim.net-1916432553-@b26.c13.bise7.blackberry>
	<4DDB54A6.9000006@postnewspapers.com.au>
Date: Tue, 24 May 2011 12:58:18 +0200
Message-ID: <BANLkTimMyHpZp0F0AX5RDFqTHRA_tChfrA@mail.gmail.com>
Subject: Re: Which version of PostgreSQL should I use.
From: Jasmin Dizdarevic <jasmin.dizdarevic@gmail.com>
To: Craig Ringer <craig@postnewspapers.com.au>, pgsql-sql@postgresql.org
Content-Type: multipart/alternative; boundary=20cf303dd4f43431b404a4037775
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.897 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RFC_ABUSE_POST=0.001
X-Spam-Level: 
X-Archive-Number: 201105/144
X-Sequence-Number: 35428

--20cf303dd4f43431b404a4037775
Content-Type: text/plain; charset=ISO-8859-1

Alright, I've misunderstood this issue. Do you have to escape bytea columns
during export or import? And how you would do this?

Ty


2011/5/24 Craig Ringer <craig@postnewspapers.com.au>

> On 24/05/11 14:30, jasmin.dizdarevic@gmail.com wrote:
> > We had trbls with our drupal site, because some settings are stored in
> bytea columns. I think lobs are a problem too, but pls see the pg_dump docs
> for details.
>
> Is it possible that you are referring to the `bytea_output' setting in
> PostgreSQL 8.4 and above?
>
> If so, the issue isn't that pg_dump somehow fails to dump the bytea
> data. Rather, it's that drupal doesn't deal well with bytea data from
> newer versions of PostgreSQL until the bytea_output setting is changed
> to 'escape' because it doesn't understand the new hex format.
>
> --
> Craig Ringer
>

--20cf303dd4f43431b404a4037775
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Alright, I&#39;ve misunderstood this issue. Do you have to escape bytea col=
umns during export or import? And how you would do this?<div><br></div><div=
>Ty</div><div><br><br><div class=3D"gmail_quote">2011/5/24 Craig Ringer <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:craig@postnewspapers.com.au">craig@pos=
tnewspapers.com.au</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;"><div class=3D"im">On 24/05/11 14:30, <a hre=
f=3D"mailto:jasmin.dizdarevic@gmail.com">jasmin.dizdarevic@gmail.com</a> wr=
ote:<br>

&gt; We had trbls with our drupal site, because some settings are stored in=
 bytea columns. I think lobs are a problem too, but pls see the pg_dump doc=
s for details.<br>
<br>
</div><div><div></div><div class=3D"h5">Is it possible that you are referri=
ng to the `bytea_output&#39; setting in<br>
PostgreSQL 8.4 and above?<br>
<br>
If so, the issue isn&#39;t that pg_dump somehow fails to dump the bytea<br>
data. Rather, it&#39;s that drupal doesn&#39;t deal well with bytea data fr=
om<br>
newer versions of PostgreSQL until the bytea_output setting is changed<br>
to &#39;escape&#39; because it doesn&#39;t understand the new hex format.<b=
r>
<br>
--<br>
Craig Ringer<br>
</div></div></blockquote></div><br></div>

--20cf303dd4f43431b404a4037775--