| From: | ljb <ljb9832(at)pobox(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Gripe: bytea_output default => data corruption |
| Date: | 2010-10-13 21:03:43 |
| Message-ID: | i956rf$228u$1@news.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-13 21:45:03 | Re: [HACKERS] Docs for archive_cleanup_command are poor |
| Previous Message | Dmitriy Igrishin | 2010-10-13 12:48:41 | Re: Gripe: bytea_output default => data corruption |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brandon Casci | 2010-10-13 21:18:10 | help with understanding EXPLAIN |
| Previous Message | Darren Duncan | 2010-10-13 21:01:16 | Re: How to search ignoring spaces and minus signs |