| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Bernd Helmle <mailings(at)oopsware(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: bytea vs. pg_dump |
| Date: | 2009-05-05 19:39:32 |
| Message-ID: | 4A0095F4.5040706@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Bernd Helmle <mailings(at)oopsware(dot)de> wrote:
>>> Another approach would be to just dump bytea columns in binary
>>> format only (not sure how doable that is, though).
>
>> If that's not doable, perhaps a base64 option for bytea COPY?
>
> I'm thinking plain old pairs-of-hex-digits might be the best
> tradeoff if conversion speed is the criterion.
That's a lot less space-efficient than base64, though.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-05 20:14:54 | Re: bytea vs. pg_dump |
| Previous Message | Robert Haas | 2009-05-05 19:30:18 | Re: Wrong stats for empty tables |