| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 07:50:25 |
| Message-ID: | D08C7A479A329583CB864EB4@teje |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--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?
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2009-05-06 10:09:21 | ToDo: Clear table counters on TRUNCATE |
| Previous Message | Greg Smith | 2009-05-06 06:17:43 | Re: Patch to fix search_path defencies with pg_bench |