From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Subject: | Re: bytea vs. pg_dump |
Date: | 2009-07-08 09:29:46 |
Message-ID: | 162867790907080229r155e0f4dofcb4f95169b3cb28@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/7/8 Bernd Helmle <mailings(at)oopsware(dot)de>:
> --On Dienstag, Juli 07, 2009 18:07:08 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> 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 ]
>
> I like the enum much better, too, but
>
> SET bytea_output = [ hex | escape ]
+ 1
Pavel
>
> looks better to me (encode/decode are using something like this already).
>
> --
> Thanks
>
> Bernd
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2009-07-08 13:43:12 | Re: *_collapse_limit, geqo_threshold |
Previous Message | Bernd Helmle | 2009-07-08 09:23:32 | Re: bytea vs. pg_dump |