| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
| Cc: | 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 12:13:03 |
| Message-ID: | 18365.1274271183@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-19 12:21:29 | Re: Stefan's bug (was: max_standby_delay considered harmful) |
| Previous Message | Robert Haas | 2010-05-19 11:50:17 | Re: Stefan's bug (was: max_standby_delay considered harmful) |