Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 726F665A72C
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Mon, 15 Mar 2010 22:53:23 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 71627-02
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 16 Mar 2010 01:53:04 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157])
	by mail.postgresql.org (Postfix) with ESMTP id A986F65A177
	for <pgsql-performance@postgresql.org>;
	Mon, 15 Mar 2010 22:53:12 -0300 (ADT)
Received: by fg-out-1718.google.com with SMTP id l26so1551713fgb.1
	for <pgsql-performance@postgresql.org>;
	Mon, 15 Mar 2010 18:53:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=9+HWRAhBbGeGY+SvJxUuj1RxCJAggvOZ9um4vKZ7CnE=;
	b=xEN9DQkN8ZClju90UvPJxnoPl0K8ZJmB5RCUOWqQq3bQG3OlcLfjOipfkhDQN2V1DD
	qk5iW4DPLYR7JBIGOsuvG8jY0gzbHv5+ztuCMHiF2dz9ETrtSQyjTWhaviQV0+pqB4kP
	6Cq71KxUM+d6JhtlXPKowQi7+W/JqjpZPuqdc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=F1yXOdOL0MMkqh/79w5SUruAgIsPZl3fDKHOxmjOEpX0VxL2rkhRkrX5q4PaPmu2u2
	x1wpMw3n98WhDG8XKRWC7+aGRp9GDXXVmeVS2qNRa6uUl3wJmdZtn0CRoHlBLOt3VZIG
	aMmPf4Xy7c7GNyWMc7/FHkCi6x8N+gmTerV8M=
MIME-Version: 1.0
Received: by 10.239.142.18 with SMTP id e18mr946884hba.181.1268704390453;
 Mon,
	15 Mar 2010 18:53:10 -0700 (PDT)
In-Reply-To: <4B9C97E1.40509@davidnewall.com>
References: <4B9C97E1.40509@davidnewall.com>
Date: Mon, 15 Mar 2010 21:53:10 -0400
Message-ID: <603c8f071003151853h155a3ebi9623f5929dacd16@mail.gmail.com>
Subject: Re: pg_dump far too slow
From: Robert Haas <robertmhaas@gmail.com>
To: David Newall <postgresql@davidnewall.com>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.457 tagged_above=-10 required=5 tests=AWL=0.142,
	BAYES_00=-2.599
X-Spam-Level: 
X-Archive-Number: 201003/158
X-Sequence-Number: 37983

On Sun, Mar 14, 2010 at 4:01 AM, David Newall
<postgresql@davidnewall.com> wrote:
> an expected 40 - 45GB of compressed output.=A0 CPU load is 100% on the co=
re
> executing pg_dump, and negligible on all others cores.=A0 The system is
> read-mostly, and largely idle.=A0 The exact invocation was:
>
> =A0=A0=A0 nohup time pg_dump -f database.dmp -Z9 database

Can you connect a few times with gdb and do "bt" to get a backtrace?
That might shed some light on where it's spending all of its time.

...Robert