Re: bytea vs. pg_dump

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Bernd Helmle <mailings(at)oopsware(dot)de>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Subject: Re: bytea vs. pg_dump
Date: 2009-08-04 14:31:26
Message-ID: 603c8f070908040731gabc747ena1b220b0090d4899@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 4, 2009 at 10:28 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)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.

Or, what we could do is start an open items for 8.5 list similar to
the one we made for 8.4. That worked pretty well, I think.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2009-08-04 14:32:57 Re: bytea vs. pg_dump
Previous Message Tom Lane 2009-08-04 14:28:48 Re: bytea vs. pg_dump