From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve McWilliams <smcwilliams@EmprisaNetworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: size of pg_dump files containing bytea values
Date: Wed, 12 Jul 2006 22:53:25 -0400
Message-ID: <1820.1152759205@sss.pgh.pa.us> (raw)
In-Reply-To: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com>
References: <3985.10.1.1.126.1152729387.squirrel@portal.emprisanetworks.com>
"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.
regards, tom lane
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: tgl@sss.pgh.pa.us, smcwilliams@EmprisaNetworks.com
Subject: Re: size of pg_dump files containing bytea values
In-Reply-To: <1820.1152759205@sss.pgh.pa.us>
* 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