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

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bernd Helmle <mailings(at)oopsware(dot)de>, Jesper Krogh <jesper(at)krogh(dot)cc>, Alex Hunsaker <badalex(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BYTEA / DBD::Pg change in 9.0 beta
Date: 2010-05-19 14:17:08
Message-ID: 4BF3F2E4.9070803@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/19/2010 08:13 AM, Tom Lane wrote:
> Bernd Helmle <mailings(at)oopsware(dot)de> writes:
>> --On 18. Mai 2010 23:20:26 +0200 Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
>>> May I ask whats the reason is for "breaking" the compatibillity?
>
>> "Efficency", if i am allowed to call it this way. The new hex
>> representation should be more efficient to retrieve and to handle than the
>> old one. I think bytea_output was set to hex for testing purposes on the
>> first hand, but not sure wether there was a consensus to leave it there
>> finally later.
>
> Yeah, we intentionally set it that way initially to help find stuff that
> needs to be updated (as DBD::Pg evidently does). It's still TBD whether
> 9.0.0 will ship with that default or not.

given how much faster the new format is (or rather how slow the old one
was) and the number of people I have seen complaining "why is bytea so
slow) I would like to see it staying turned on by default. However this
also depends on how quickly database driver developers can adapt.

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bogdan Vlad 2010-05-19 14:50:29 C function argument types
Previous Message Robert Haas 2010-05-19 13:03:19 Re: Stefan's bug (was: max_standby_delay considered harmful)