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

From Erik Jones
Subject Re: Rapidly decaying performance repopulating a large table
Date
Msg-id A699AFB9-C560-4536-B6E3-FE7A66771AE8@myemma.com
Whole thread Raw
In response to Re: Rapidly decaying performance repopulating a large table  ("David Wilson" <david.t.wilson@gmail.com>)
List pgsql-general
On Apr 22, 2008, at 4:46 PM, David Wilson wrote:

> On Tue, Apr 22, 2008 at 5:18 PM, Scott Marlowe <scott.marlowe@gmail.com
> > wrote:
>>
>> Try upping your checkpoint segments.  Some folks find fairly large
>> numbers like 50 to 100 to be helpful.  Each segment = 16Megs, so be
>> sure not to run your system out of drive space while increasing it.
>>
>
> Ahh, much more progress. 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. Thanks for the
> help. Any other random thoughts while you're at it? :)

Has anyone yet pointed out the standards:  drop indexes and foreign
keys and rebuild them once the entire data import is finished?

Erik Jones

DBA | Emma®
erik@myemma.com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com




pgsql-general by date:

Previous
From: Erik Jones
Date:
Subject: Re: Schema migration tools?
Next
From: Tom Lane
Date:
Subject: Re: Rapidly decaying performance repopulating a large table