From: Simon Riggs <simon@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Karim Nassar <karim.nassar@NAU.EDU>
Cc: pgsql-performance@postgresql.org
Subject: Re: Delete query takes exorbitant amount of time
Date: Mon, 28 Mar 2005 23:59:11 +0100
Message-ID: <1112050751.11750.924.camel@localhost.localdomain> (raw)
In-Reply-To: <200503250938.28896.josh@agliodbs.com>
References: <1111709457.9085.127.camel@k2.cet.nau.edu>
<200503242124.39558.josh@agliodbs.com>
<1111728955.9085.238.camel@k2.cet.nau.edu>
<200503250938.28896.josh@agliodbs.com>
On Fri, 2005-03-25 at 09:38 -0800, Josh Berkus wrote:
> > I guess I was wondering if there is other general tuning advice for such
> > large table indexes such as increasing statistics, etc.
>
> 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?
>
In 8.0, maintenance_work_mem is used for index creation, vacuum and
initial check of FK checks at time of creation. Everything else uses
work_mem as the limit.
Best Regards, Simon Riggs
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: simon@2ndquadrant.com, josh@agliodbs.com, karim.nassar@NAU.EDU
Subject: Re: Delete query takes exorbitant amount of time
In-Reply-To: <1112050751.11750.924.camel@localhost.localdomain>
* 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