Re: bytea vs. pg_dump
От | Pavel Stehule |
---|---|
Тема | Re: bytea vs. pg_dump |
Дата | |
Msg-id | 162867790907080229r155e0f4dofcb4f95169b3cb28@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: bytea vs. pg_dump (Bernd Helmle <mailings@oopsware.de>) |
Список | pgsql-hackers |
2009/7/8 Bernd Helmle <mailings@oopsware.de>: > --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 ] + 1 Pavel > > looks better to me (encode/decode are using something like this already). > > -- > Thanks > > Bernd > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers >
В списке pgsql-hackers по дате отправления: