From: Robert Haas <robertmhaas@gmail.com>
To: David Newall <postgresql@davidnewall.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: pg_dump far too slow
Date: Mon, 15 Mar 2010 21:53:10 -0400
Message-ID: <603c8f071003151853h155a3ebi9623f5929dacd16@mail.gmail.com> (raw)
In-Reply-To: <4B9C97E1.40509@davidnewall.com>
References: <4B9C97E1.40509@davidnewall.com>
On Sun, Mar 14, 2010 at 4:01 AM, David Newall
<postgresql@davidnewall.com> wrote:
> an expected 40 - 45GB of compressed output. CPU load is 100% on the core
> executing pg_dump, and negligible on all others cores. The system is
> read-mostly, and largely idle. The exact invocation was:
>
> 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
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-performance@postgresql.org
Cc: robertmhaas@gmail.com, postgresql@davidnewall.com
Subject: Re: pg_dump far too slow
In-Reply-To: <603c8f071003151853h155a3ebi9623f5929dacd16@mail.gmail.com>
* 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