Re: Rapidly decaying performance repopulating a large table

From: Erik Jones <erik(at)myemma(dot)com>
To: David Wilson <david(dot)t(dot)wilson(at)gmail(dot)com>
Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Rapidly decaying performance repopulating a large table
Date: 2008-04-22 22:01:51
Message-ID: A699AFB9-C560-4536-B6E3-FE7A66771AE8@myemma.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)marlowe(at)gmail(dot)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(at)myemma(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-04-22 22:10:55 Re: Rapidly decaying performance repopulating a large table
Previous Message Erik Jones 2008-04-22 21:59:32 Re: Schema migration tools?