Re: bytea vs. pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: bytea vs. pg_dump
Date
Msg-id 29611.1247004428@sss.pgh.pa.us
Whole thread Raw
In response to Re: bytea vs. pg_dump  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: bytea vs. pg_dump  (Bernd Helmle <mailings@oopsware.de>)
Re: bytea vs. pg_dump  (Peter Eisentraut <peter_e@gmx.net>)
List 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 by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: bytea vs. pg_dump
Next
From: Alvaro Herrera
Date:
Subject: Re: *_collapse_limit, geqo_threshold