Re: bytea vs. pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: bytea vs. pg_dump
Date
Msg-id 16451.1241534313@sss.pgh.pa.us
Whole thread Raw
In response to Re: bytea vs. pg_dump  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: bytea vs. pg_dump  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: bytea vs. pg_dump  (Andrew Dunstan <andrew@dunslane.net>)
Re: bytea vs. pg_dump  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: bytea vs. pg_dump  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Bernd Helmle <mailings@oopsware.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.  The main problem
in any case would be to decide how to control the format option.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: bytea vs. pg_dump
Next
From: Alvaro Herrera
Date:
Subject: Re: bytea vs. pg_dump