| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: bytea vs. pg_dump |
| Date: | 2009-05-06 11:30:04 |
| Message-ID: | 4A0174BC.3010106@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bernd Helmle wrote:
> --On Dienstag, Mai 05, 2009 16:57:50 -0400 Andrew Dunstan
> <andrew(at)dunslane(dot)net> wrote:
>
>> Hex will already provide some space savings over our current encoding
>> method for most byteas anyway. It's not like we'd be making things less
>> efficient space-wise. And in compressed archives the space difference is
>> likely to dissolve to not very much, I suspect.
>
> I'm dumb: I don't understand why a hex conversion would be
> significantly faster than what we have now?
>
Quite apart from anything else you would not need the current loop over
the bytea input to calculate the result length - in hex it would just be
the input length * 2.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-05-06 11:51:14 | Re: bytea vs. pg_dump |
| Previous Message | Bernd Helmle | 2009-05-06 11:14:43 | Re: Values of fields in Rules |