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

From Tom Lane
Subject Re: bytea vs. pg_dump
Date
Msg-id 6463.1249326668@sss.pgh.pa.us
Whole thread Raw
In response to Re: bytea vs. pg_dump  (Bernd Helmle <mailings@oopsware.de>)
Responses Re: bytea vs. pg_dump  (Bernd Helmle <mailings@oopsware.de>)
Re: bytea vs. pg_dump  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Bernd Helmle <mailings@oopsware.de> writes:
> --On Samstag, Juli 11, 2009 13:40:44 +0300 Peter Eisentraut 
> <peter_e@gmx.net> wrote:
>> OK, here is an updated patch.  It has the setting as enum, completed
>> documentation, and libpq support.  I'll add it to the commit fest in the
>> hope  that someone else can look it over in detail.

> I've attached a slightly edited patch which fixes a compiler warning in 
> encode.c, too.

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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Alpha releases: How to tag
Next
From: Steve Prentice
Date:
Subject: Re: mixed, named notation support