From: | Pavel Golub <pavel(at)microolap(dot)com> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: bytea vs. pg_dump |
Date: | 2009-07-09 12:52:05 |
Message-ID: | 1394226912.20090709155205@gf.microolap.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello, Bernd.
You wrote:
BH> --On Dienstag, Juli 07, 2009 18:07:08 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)gf(dot)microolap(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-07-09 13:40:53 | Re: *_collapse_limit, geqo_threshold |
Previous Message | Noah Misch | 2009-07-09 12:23:28 | Re: *_collapse_limit, geqo_threshold |