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

From Pavel Golub
Subject Re: bytea vs. pg_dump
Date
Msg-id 1394226912.20090709155205@gf.microolap.com
Whole thread Raw
In response to Re: bytea vs. pg_dump  (Bernd Helmle <mailings@oopsware.de>)
List pgsql-hackers
Hello, Bernd.

You wrote:

BH> --On Dienstag, Juli 07, 2009 18:07:08 -0400 Tom Lane <tgl@sss.pgh.pa.us>
BH> wrote:

>> Enum.  If we do this then it seems entirely fair that someone might
>> want other settings someday.  Also, it seems silly to pick a format
>> partly on the grounds that it's expansible, and then not make the
>> control GUC expansible.  Perhaps
>>
>>       SET bytea_output = [ hex | traditional ]

BH> I like the enum much better, too, but

BH>         SET bytea_output = [ hex | escape ]

BH> looks better to me (encode/decode are using something like this already).

BH> -- 
BH>   Thanks

BH>                     Bernd


Yeah, this looks nice for me too

-- 
With best wishes,Pavel                          mailto:pavel@gf.microolap.com



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby
Next
From: "Kevin Grittner"
Date:
Subject: Re: *_collapse_limit, geqo_threshold