Re: bytea vs. pg_dump
| От | Tom Lane |
|---|---|
| Тема | Re: bytea vs. pg_dump |
| Дата | |
| Msg-id | 29611.1247004428@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: bytea vs. pg_dump (Peter Eisentraut <peter_e@gmx.net>) |
| Ответы |
Re: bytea vs. pg_dump
Re: bytea vs. pg_dump |
| Список | pgsql-hackers |
Peter Eisentraut <peter_e@gmx.net> writes:
> Here is a first cut at a new hex bytea input and output format. Example:
> ...
> SET bytea_output_hex = true;
> Should the configuration parameter be a boolean or an enum, opening
> possibilities for other formats?
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 ]
regards, tom lane
В списке pgsql-hackers по дате отправления: