* Greg Stark:
> Didn't byteas used to get printed as hex?
No, they didn't. It would be useful to support hexadecimal BYTEA
literals, though. Unfortunately, X'DEADBEEF' has already been taken
by bit strings.
--
Florian Weimer<[EMAIL PROTECTED]>
BFK edv-consulting GmbH htt
Greg Stark <[EMAIL PROTECTED]> writes:
> Didn't byteas used to get printed as hex?
No, not that I recall. I don't have anything older than 7.0 running,
but it behaves the same as now:
play=> select 'xyz\\001'::bytea;
?column?
--
xyz\001
(1 row)
play=>
regards,
Tom Lane <[EMAIL PROTECTED]> writes:
> "Steve McWilliams" <[EMAIL PROTECTED]> writes:
> > I notice that non-printables in bytea values are being spit out by pg_dump
> > using escaped octet sequences even when the "-Fc" option is present
> > specifying use of the custom binary output format rather
"Steve McWilliams" <[EMAIL PROTECTED]> writes:
> I notice that non-printables in bytea values are being spit out by pg_dump
> using escaped octet sequences even when the "-Fc" option is present
> specifying use of the custom binary output format rather than plain text
> format. This bloats the siz
I notice that non-printables in bytea values are being spit out by pg_dump
using escaped octet sequences even when the "-Fc" option is present
specifying use of the custom binary output format rather than plain text
format. This bloats the size of bytea values in the dump file by a factor
of 3+ ty
