Re: BYTEA / DBD::Pg change in 9.0 beta

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Jesper Krogh <jesper(at)krogh(dot)cc>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: BYTEA / DBD::Pg change in 9.0 beta
Date: 2010-05-18 21:12:52
Message-ID: AANLkTilCJosQcZYZCsI4tlUInkjzoccazUIJC2DsVajj@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 18, 2010 at 14:54, Jesper Krogh <jesper(at)krogh(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-05-18 21:16:24 Re: pg_upgrade - link mode and transaction-wraparound data loss
Previous Message Heikki Linnakangas 2010-05-18 21:08:13 Re: Keepalive for max_standby_delay