Re: size of pg_dump files containing bytea values
- From: Greg Stark <gsstark(at)mit(dot)edu>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: size of pg_dump files containing bytea values
- Date: 13 Jul 2006 12:30:50 -0400
- Message-id: <87k66hii11.fsf@stark.xeocode.com> <text/plain>
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> "Steve McWilliams" <smcwilliams(at)EmprisaNetworks(dot)com> 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 size of bytea values in the dump file by a factor
> > of 3+ typically.
>
> No, because the subsequent compression step should buy back most of
> that.
Didn't byteas used to get printed as hex? Even in psql they're now being
printed in the escaped octet sequence. When did this change?
--
greg
Home |
Main Index |
Thread Index