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

From Merlin Moncure
Subject Re: bytea vs. pg_dump
Date
Msg-id b42b73150905060451w1aa96b8dm7f53a30cce11bcc4@mail.gmail.com
Whole thread Raw
In response to Re: bytea vs. pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bytea vs. pg_dump  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Tue, May 5, 2009 at 4:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> Tom Lane wrote:
>>> 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.
>
> Well, base64 could give a 33% savings, but it's significantly harder
> to encode/decode.  Also, since it has a much larger set of valid
> data characters, it would be *much* more likely to allow old-style
> formatting to be mistaken for new-style.  Unless we can think of
> a more bulletproof format selection mechanism, that could be
> an overriding consideration.

another nit with base64 is that properly encoded data requires
newlines according to the standard.

merlin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: bytea vs. pg_dump
Next
From: Andrew Dunstan
Date:
Subject: Re: bytea vs. pg_dump