Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 357BE2E004D for ; Sat, 12 Apr 2008 23:46:11 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 59806-10 for ; Sat, 12 Apr 2008 23:46:08 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by developer.postgresql.org (Postfix) with ESMTP id 0C8A22E002E for ; Sat, 12 Apr 2008 23:46:07 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m3D2k6IL014645; Sat, 12 Apr 2008 22:46:06 -0400 (EDT) To: "Ryan Wells" cc: pgsql-admin@postgresql.org Subject: Re: Slow pg_dump In-reply-to: References: <9CC13EC943102E46BA4E328F9FBCDB36255FB57B@exchange.DOCS.COM> Comments: In-reply-to "Ryan Wells" message dated "Sat, 12 Apr 2008 19:59:09 -0500" Date: Sat, 12 Apr 2008 22:46:06 -0400 Message-ID: <14644.1208054766@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/113 X-Sequence-Number: 28877 "Ryan Wells" 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