From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ryan Wells <ryan.wells@soapware.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Slow pg_dump
Date: Sat, 12 Apr 2008 22:46:06 -0400
Message-ID: <14644.1208054766@sss.pgh.pa.us> (raw)
In-Reply-To: <EE6D03C0EF73D14E8034C37CA9B6277401DA03@exchange.DOCS.COM>
References: <9CC13EC943102E46BA4E328F9FBCDB36255FB57B@exchange.DOCS.COM>
<EE6D03C0EF73D14E8034C37CA9B6277401DA03@exchange.DOCS.COM>
"Ryan Wells" <ryan.wells@soapware.com> writes:
> We have several tables that are used to store binary data as bytea (in
> this example image files),
Precompressed image formats, no doubt?
> pg_dump -i -h localhost -p 5432 -U postgres -F c -v -f "backupTest.backup" -t "public"."images" db_name
Try it with -Z0, or even drop the -Fc completely, since it's certainly
not very helpful on a single-table dump. Re-compressing already
compressed data is not only useless but impressively slow ...
Also, drop the -i, that's nothing but a foot-gun.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ryan.wells@soapware.com
Subject: Re: Slow pg_dump
In-Reply-To: <14644.1208054766@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