From: | Rajesh Kumar Mallah <mallah(dot)rajesh(at)gmail(dot)com> |
---|---|
To: | ljb <ljb9832(at)pobox(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Gripe: bytea_output default => data corruption |
Date: | 2010-10-14 09:19:13 |
Message-ID: | AANLkTi=SH6s3FcsCf0quZm09-XgncTnQPR18-Z6GVqsU@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Dear Griper!,
fortunately someone showed a easy 'fix'
ALTER DATABASE foo SET bytea_output='escape' ;
Regds
Rajesh Kumar Mallah.
On Wed, Oct 13, 2010 at 5:03 PM, ljb <ljb9832(at)pobox(dot)com> wrote:
> rod(at)iol(dot)ie wrote:
>>...
>> In fairness, it *is* flagged in the release note - it's the first item
>> under "data types" in the list of incompatibilities.
>
> Quote:
> "bytea output now appears in hex format by default (Peter Eisentraut)
> The server parameter bytea_output can be used to select the
> traditional output format if needed for compatibility."
>
> This is inadequate, because it fails to warn that pre-9.0 clients will
> decode the data incorrectly without reporting an error.
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-10-14 12:50:07 | Re: Documenting removal of nonnullvalue() and friends |
Previous Message | Raymond O'Donnell | 2010-10-14 09:15:46 | Re: Gripe: bytea_output default => data corruption |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2010-10-14 09:32:16 | Re: How to iterate fields into a NEW.* RECORD in a TRIGGER procedure ? |
Previous Message | Raymond O'Donnell | 2010-10-14 09:15:46 | Re: Gripe: bytea_output default => data corruption |