| From: | Raymond O'Donnell <rod(at)iol(dot)ie> |
|---|---|
| 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:15:46 |
| Message-ID: | 4CB6CA42.2020305@iol.ie |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On 13/10/2010 22:03, ljb 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.
I thought myself that the word "incompatibility" was fairly
self-explanatory... :-)
Ray.
--
Raymond O'Donnell :: Galway :: Ireland
rod(at)iol(dot)ie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2010-10-14 09:19:13 | Re: Gripe: bytea_output default => data corruption |
| Previous Message | Josh Kupershmidt | 2010-10-14 03:25:25 | Re: Documenting removal of nonnullvalue() and friends |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2010-10-14 09:19:13 | Re: Gripe: bytea_output default => data corruption |
| Previous Message | Rajesh Kumar Mallah | 2010-10-14 09:15:22 | Re: Adding a New Column Specifically In a Table |