Re: database response slows while pg_dump is running (8.4.2)

From: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: database response slows while pg_dump is running (8.4.2)
Date: 2010-06-10 21:49:58
Message-ID: AANLkTil9sSnHt4BxXiOUTJG4sUt1VozEmUBL51DS1640@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jun 10, 2010 at 1:25 PM, Aleksey Tsalolikhin
<atsaloli(dot)tech(at)gmail(dot)com> wrote:
> PostgreSQL 8.4.2 response time slows during pg_dump of a 14 GB database.
>
...
>
> Is there any way I can keep my response fast but still get my pg_dump?
> Or should I move my pg_dump to a Slony-I slave?

Thank you for your kind replies.

More data:

1. We're not dumping across the network. The pg_dump
process runs on the same physical server as PostgreSQL.

2. We're not CPU bound - CPU utilization goes from 95% idle
to 75% idle during the pg_dump.

3. We ARE disk bound. Disk utilization goes to 94% during
the dump. There is an order of magnitude more reads than
writes.

Greg, I didn't see anything in the "I/O" section of
http://wiki.postgresql.org/wiki/Priorities I could use.
We ionice our pg_dump process, but it's a PostgreSQL
process that stresses the disk.

Thanks anyway - glad to hear dumping from a slave is
a popular approach, that's what we'll do. This is good,
it'll allow us to increase our pg_dumps from 1 a day to
as many as we want to feel safe.

Best,
-at

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Christensen 2010-06-10 21:59:50 Re: Best way to store case-insensitive data?
Previous Message Scott Marlowe 2010-06-10 21:42:17 Re: Best way to store case-insensitive data?