pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Karim Nassar <karim.nassar@NAU.EDU>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Delete query takes exorbitant amount of time
Date: Thu, 24 Mar 2005 22:35:55 -0700
Message-ID: <1111728955.9085.238.camel@k2.cet.nau.edu> (raw)
In-Reply-To: <200503242124.39558.josh@agliodbs.com>
References: <1111709457.9085.127.camel@k2.cet.nau.edu>
	<2630.1111711927@sss.pgh.pa.us>
	<1111715304.9089.179.camel@k2.cet.nau.edu>
	<200503242124.39558.josh@agliodbs.com>

On Thu, 2005-03-24 at 21:24 -0800, Josh Berkus wrote:
> Karim,
> How about getting some decent disk support?  A single 10K SCSI disk is a bit 
> sub-par for a database with 100's of millions of records.  Too bad you didn't 
> get a v40z ...

Hehe. I have one I am setting up that will be dedicated to postgresql,
hence my question about a week ago about disk partitioning/striping :-)


> Beyond that, you'll want to do the same thing whenever you purge the 
> referencing table; drop keys, delete, re-create keys.  Or think about why it 
> is you need to delete batches of records from this FKed table at all.

The database is for weather data from multiple sources. When adding a
new dataset, I have to create/test/delete/recreate the config in the
FKed table. Users don't have this power, but I need it.
Drop/delete/recreate is a totally acceptable solution for this scenario.

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

Thanks,
-- 
Karim Nassar
Department of Computer Science
Box 15600, College of Engineering and Natural Sciences
Northern Arizona University,  Flagstaff, Arizona 86011
Office: (928) 523-5868 -=- Mobile: (928) 699-9221




view thread (60+ messages)  latest in thread

Message-ID: <1111728955.9085.238.camel@k2.cet.nau.edu>
Permalink:  ../1111728955.9085.238.camel@k2.cet.nau.edu/
Also on:    postgresql.org/message-id/1111728955.9085.238.camel@k2.cet.nau.edu

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: karim.nassar@NAU.EDU, josh@agliodbs.com
  Subject: Re: Delete query takes exorbitant amount of time
  In-Reply-To: <1111728955.9085.238.camel@k2.cet.nau.edu>
  References: <1111709457.9085.127.camel@k2.cet.nau.edu> <2630.1111711927@sss.pgh.pa.us> <1111715304.9089.179.camel@k2.cet.nau.edu> <200503242124.39558.josh@agliodbs.com> <1111728955.9085.238.camel@k2.cet.nau.edu>

* 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