From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Karim Nassar <karim.nassar@NAU.EDU>
Subject: Re: Delete query takes exorbitant amount of time
Date: Fri, 25 Mar 2005 09:38:28 -0800
User-Agent: KMail/1.6.2
Cc: pgsql-performance@postgresql.org
References: <1111709457.9085.127.camel@k2.cet.nau.edu>
	<200503242124.39558.josh@agliodbs.com>
	<1111728955.9085.238.camel@k2.cet.nau.edu>
In-Reply-To: <1111728955.9085.238.camel@k2.cet.nau.edu>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <200503250938.28896.josh@agliodbs.com>

Karim,

> I guess I was wondering if there is other general tuning advice for such
> large table indexes such as increasing statistics, etc.

Well, your index use problem is being explained by Tom, Stephan and Simon; 
basically your FKed data types are incompatible for index use purposes so the 
system *can't* use an index while loading.

If you're going with the drop/load/recreate option, then I'd suggest 
increasing work_mem for the duration.  Hmmm ... or maintenance_work_mem?  
What gets used for FK checks?  Simon?

-- 
Josh Berkus
Aglio Database Solutions
San Francisco