Re: bytea vs. pg_dump
| От | Bernd Helmle |
|---|---|
| Тема | Re: bytea vs. pg_dump |
| Дата | |
| Msg-id | 07F7ECE41BBB79F44E6C0ECD@teje обсуждение исходный текст |
| Ответ на | Re: bytea vs. pg_dump (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: bytea vs. pg_dump
Re: bytea vs. pg_dump |
| Список | pgsql-hackers |
--On Dienstag, Juli 07, 2009 18:07:08 -0400 Tom Lane <tgl@sss.pgh.pa.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 ]
looks better to me (encode/decode are using something like this already).
-- Thanks
Bernd
В списке pgsql-hackers по дате отправления: