Re: BYTEA / DBD::Pg change in 9.0 beta - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: BYTEA / DBD::Pg change in 9.0 beta
Date
Msg-id AANLkTilCJosQcZYZCsI4tlUInkjzoccazUIJC2DsVajj@mail.gmail.com
Whole thread Raw
In response to BYTEA / DBD::Pg change in 9.0 beta  (Jesper Krogh <jesper@krogh.cc>)
Responses Re: BYTEA / DBD::Pg change in 9.0 beta
List pgsql-hackers
On Tue, May 18, 2010 at 14:54, Jesper Krogh <jesper@krogh.cc> wrote:
> Hi.
>
> I'm trying to do a test move of one of our applications onto 9.0beta1.
> We use storable and serializes data into a bytea column in the database.
> [ snip insert/select using bytea ]

> 8.4
>  id |                                       testbytea
> ----+----------------------------------------------------------------------------------------
>  9 |
> \005\007\003\000\000\000\002\012\0012\000\000\000\004that\012\0011\000\000\000\004this
> (1 row)
>
> 9.0beta1
>  id |                          testbytea
> ----+--------------------------------------------------------------
>  3 | \x050703000000020a013200000004746861740a01310000000474686973
> (1 row)


Try adding $db->do("set bytea_output 'escape';"); as 9.0 defaults to
hex encoding.  Id bet DBD::Pg does not account for that yet.


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Keepalive for max_standby_delay
Next
From: Caleb Welton
Date:
Subject: Re: Bug with ordering aggregates?