From: Greg Stark <gsstark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Steve McWilliams <smcwilliams@EmprisaNetworks.com>
Cc: pgsql-performance@postgresql.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> (raw)
In-Reply-To: <1820.1152759205@sss.pgh.pa.us>
References: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com>
<1820.1152759205@sss.pgh.pa.us>
Tom Lane <tgl@sss.pgh.pa.us> writes:
> "Steve McWilliams" <smcwilliams@EmprisaNetworks.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsstark@mit.edu, tgl@sss.pgh.pa.us, smcwilliams@EmprisaNetworks.com
Subject: Re: size of pg_dump files containing bytea values
In-Reply-To: <87k66hii11.fsf@stark.xeocode.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox