From: | Jasmin Dizdarevic <jasmin(dot)dizdarevic(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Which version of PostgreSQL should I use. |
Date: | 2011-05-24 10:58:18 |
Message-ID: | BANLkTimMyHpZp0F0AX5RDFqTHRA_tChfrA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)postnewspapers(dot)com(dot)au>
> On 24/05/11 14:30, jasmin(dot)dizdarevic(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jasmin Dizdarevic | 2011-05-24 11:45:36 | Re: Performance of NOT IN and <> with PG 9.0.4 |
Previous Message | Jasmin Dizdarevic | 2011-05-24 10:49:34 | Re: Performance of NOT IN and <> with PG 9.0.4 |