From: Jasmin Dizdarevic <jasmin.dizdarevic@gmail.com>
To: Craig Ringer <craig@postnewspapers.com.au>
To: pgsql-sql@postgresql.org
Subject: Re: Which version of PostgreSQL should I use.
Date: Tue, 24 May 2011 12:58:18 +0200
Message-ID: <BANLkTimMyHpZp0F0AX5RDFqTHRA_tChfrA@mail.gmail.com> (raw)
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>
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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jasmin.dizdarevic@gmail.com, craig@postnewspapers.com.au
Subject: Re: Which version of PostgreSQL should I use.
In-Reply-To: <BANLkTimMyHpZp0F0AX5RDFqTHRA_tChfrA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox