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

From Tom Lane
Subject Re: bytea vs. pg_dump
Date
Msg-id 22619.1249396128@sss.pgh.pa.us
Whole thread Raw
In response to Re: bytea vs. pg_dump  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: bytea vs. pg_dump  (Robert Haas <robertmhaas@gmail.com>)
Re: bytea vs. pg_dump  (Bernd Helmle <mailings@oopsware.de>)
Re: bytea vs. pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On Monday 03 August 2009 22:11:08 Tom Lane wrote:
>> I'm starting to look at this patch.  I observe that it's setting the
>> default output format to HEX.  If changing the default behavior was
>> agreed to, or even discussed, I do not remember where.  Shouldn't the
>> default stay the same?

> I did pose that question in my patch submission email.

> Unless there is overwhelming support in favor of changing, we probably 
> shouldn't change it, at least not yet.

While I've been poking at the pg_dump issues, it's occurred to me that
changing the default would be a great forcing function for finding out
any lurking problems.  What I'm inclined to do now is to commit it
*with* the change of default, and let it be that way at least for a
few alpha-test releases.  We can vote on whether to switch the default
back before 8.5 final.

If this seems reasonable, I can make a note of the point in the commit
message, so that we won't forget when the time comes.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Alpha Releases: Docs?
Next
From: Robert Haas
Date:
Subject: Re: bytea vs. pg_dump