From: Josh Berkus <josh@agliodbs.com>
To: Karim Nassar <karim.nassar@NAU.EDU>
Cc: pgsql-performance@postgresql.org
Subject: Re: Delete query takes exorbitant amount of time
Date: Fri, 25 Mar 2005 09:38:28 -0800
Message-ID: <200503250938.28896.josh@agliodbs.com> (raw)
In-Reply-To: <1111728955.9085.238.camel@k2.cet.nau.edu>
References: <1111709457.9085.127.camel@k2.cet.nau.edu>
<200503242124.39558.josh@agliodbs.com>
<1111728955.9085.238.camel@k2.cet.nau.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, karim.nassar@NAU.EDU
Subject: Re: Delete query takes exorbitant amount of time
In-Reply-To: <200503250938.28896.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox