From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Andy Colson <andy(at)squeakycode(dot)net> |
Cc: | Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: database response slows while pg_dump is running (8.4.2) |
Date: | 2010-06-10 21:28:38 |
Message-ID: | AANLkTimp_lIlqJ1VZwbl4H6wO_u6jPhMAyCM5nyHxSS9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 10, 2010 at 3:22 PM, Andy Colson <andy(at)squeakycode(dot)net> wrote:
> On 6/10/2010 3:25 PM, Aleksey Tsalolikhin wrote:
>>
>> PostgreSQL 8.4.2 response time slows during pg_dump of a 14 GB database.
>>
>> Specifically, I am monitoring how long it takes to login to our Web
>> app - usually under 2 seconds, but when pg_dump is running, that
>> changes to 2 - 18 seconds.
>>
>> 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?
>>
>> Best,
>> -at
>>
>
> It depends:
> if you are cpu bound, you could try nice.
> if you are network bound then dont pg_dump across the network
> if you are io bound, pg_dump to a different drive, or pg_dump across
> the network.
>
>
> Isnt the slave a backup anyway? Do you need another dump?
Replication does not equal backup. For instance how would you recover
from "delete from table" with no where clause with replication?
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Christensen | 2010-06-10 21:29:37 | Re: Best way to store case-insensitive data? |
Previous Message | Steve Atkins | 2010-06-10 21:26:25 | Re: Best way to store case-insensitive data? |