Re: Delete query takes exorbitant amount of time

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Karim Nassar <karim(dot)nassar(at)NAU(dot)EDU>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Delete query takes exorbitant amount of time
Date: 2005-03-28 22:59:11
Message-ID: 1112050751.11750.924.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2005-03-28 23:37:54 Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
Previous Message Dave Held 2005-03-28 22:58:55 JDBC best practice