X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 947573A6340 for ; Sat, 11 Dec 2004 16:37:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75925-07 for ; Sat, 11 Dec 2004 16:37:55 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id EBBC93A631B for ; Sat, 11 Dec 2004 16:37:54 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iBBGbolZ016683; Sat, 11 Dec 2004 11:37:51 -0500 (EST) To: "John Jensen" Cc: gspiegelberg@cranel.com, pgsql-admin@postgresql.org Subject: Re: Backup is too slow In-reply-to: References: Comments: In-reply-to "John Jensen" message dated "Tue, 07 Dec 2004 15:31:08 +0000" Date: Sat, 11 Dec 2004 11:37:50 -0500 Message-ID: <16682.1102783070@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/85 X-Sequence-Number: 15671 "John Jensen" writes: > The job is clearly cpu bound in the postmaster process. Which part of the dump process is CPU bound --- dumping schema, or data? (Try enabling log_statement for the pg_dump run and correlating the appearance of queries in the postmaster log with the CPU usage.) If it's schema-bound, maybe you need to vacuum/analyze your system catalogs a bit more aggressively. If it's data-bound, I'm not sure what you can do other than switch to datatypes that are cheaper to convert to text form. It would be interesting to find out where the problem is, though, in case there's something we can fix for future releases. regards, tom lane