Re: Rapidly decaying performance repopulating a large table - Mailing list pgsql-general

From Tomasz Ostrowski
Subject Re: Rapidly decaying performance repopulating a large table
Date
Msg-id 480F193E.7090407@batory.org.pl
Whole thread Raw
In response to Re: Rapidly decaying performance repopulating a large table  ("David Wilson" <david.t.wilson@gmail.com>)
Responses Re: Rapidly decaying performance repopulating a large table  ("David Wilson" <david.t.wilson@gmail.com>)
List pgsql-general
On 2008-04-22 23:46, David Wilson wrote:

> Upping the segments to 50, timeout to 30m and completion target to
> 0.9 has improved average copy time to between 2 and 10 seconds, which
> is definitely an improvement.

I'd up them to 128 (or even 256) and set completion target back to 0.5.
But make sure you'll always have 4GB (8GB) of disk space for wal logs.

All you'd risk is several minutes of recovering in case of server crash.

Regards
Tometzky
--
...although Eating Honey was a very good thing to do, there was a
moment just before you began to eat it which was better than when you
were...
                                                      Winnie the Pooh

pgsql-general by date:

Previous
From: Pascal Cohen
Date:
Subject: Deny creation of tables for a user
Next
From: Terry Lee Tucker
Date:
Subject: Re: Deny creation of tables for a user