Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id 32C252E0060 for ; Fri, 18 Apr 2008 12:45:18 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 71346-03 for ; Fri, 18 Apr 2008 12:45:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from exchange.DOCS.COM (exchange.docs.com [75.13.188.5]) by developer.postgresql.org (Postfix) with ESMTP id 940BF2E0057 for ; Fri, 18 Apr 2008 12:45:15 -0300 (ADT) Content-class: urn:content-classes:message Subject: Re: pg_dump Performance MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 18 Apr 2008 10:45:13 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pg_dump Performance Thread-Index: AcicRsQ2KtAJv4NNS9Wi+9C7pSTgkQFJEj8Q References: From: "Ryan Wells" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.823 tagged_above=0 required=5 tests=AWL=0.823 X-Spam-Level: X-Archive-Number: 200804/193 X-Sequence-Number: 28957 Sorry for the double post. Our email server had some problems overnight. Feel free to ignore this. We're still working on the issue using suggestions from last week, and we're seeing some improvements. Ryan=20 -----Original Message----- From: Ryan Wells=20 Sent: Friday, April 11, 2008 9:42 PM To: pgsql-admin@postgresql.org Subject: pg_dump Performance We're having what seem like serious performance issues with pg_dump, and I hope someone can help. =20 We have several tables that are used to store binary data as bytea (in this example image files), but we're having similar time issues with text tables as well. In my most recent test, the sample table was about 5 GB in 1644 rows, with image files sizes between 1 MB and 35 MB. The server was a 3.0 GHz P4 running WinXP, with 2 GB of ram, the backup stored to a separate disk from the data, and little else running on the sytem. We're doing the following: =20 pg_dump -i -h localhost -p 5432 -U postgres -F c -v -f "backupTest.backup" -t "public"."images" db_name In the test above, this took 1hr 45min to complete. Since we expect to have users with 50-100GB of data, if not more, backup times that take nearly an entire day are unacceptable. We think there must be something we're doing wrong, but none of our searches have turned up anything (we likely just don't know the right search terms). Hopefully, either there's a server setting or pg_dump option we need to change, but we're open to design changes if necessary. Can anyone who has dealt with this before advise us? Thanks! Ryan =20