| 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: | 2006-07-13 16:30:50 |
| Message-ID: | 87k66hii11.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-13 17:11:56 | Re: hyper slow after upgrade to 8.1.4 |
| Previous Message | Tom Lane | 2006-07-13 14:44:19 | Re: Sun Donated a Sun Fire T2000 to the PostgreSQL |