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

From Bernd Helmle
Subject Re: bytea vs. pg_dump
Date
Msg-id 07F7ECE41BBB79F44E6C0ECD@teje
Whole thread Raw
In response to Re: bytea vs. pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bytea vs. pg_dump
Re: bytea vs. pg_dump
List 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 by date:

Previous
From: Jan Urbański
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Dean Rasheed
Date:
Subject: Re: WIP: Deferrable unique constraints