From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Wampler <swampler@noao.edu>
Cc: Postgres-performance <pgsql-performance@postgresql.org>
Subject: Re: Help speeding up delete
Date: Mon, 14 Nov 2005 18:42:43 -0500
Message-ID: <4162.1132011763@sss.pgh.pa.us> (raw)
In-Reply-To: <43790A99.9050603@noao.edu>
References: <43790A99.9050603@noao.edu>
Steve Wampler <swampler@noao.edu> writes:
> We've got an older system in production (PG 7.2.4). Recently
> one of the users has wanted to implement a selective delete,
> but is finding that the time it appears to take exceeds her
> patience factor by several orders of magnitude. Here's
> a synopsis of her report. It appears that the "WHERE
> id IN ..." is resulting in a seq scan that is causing
> the problem, but we're not SQL expert enough to know
> what to do about it.
> Can someone point out what we're doing wrong, or how we
> could get a (much) faster delete? Thanks!
Update to 7.4 or later ;-)
Quite seriously, if you're still using 7.2.4 for production purposes
you could justifiably be accused of negligence. There are three or four
data-loss-grade bugs fixed in the later 7.2.x releases, not to mention
security holes; and that was before we abandoned support for 7.2.
You *really* need to be thinking about an update.
regards, tom lane
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: tgl@sss.pgh.pa.us, swampler@noao.edu
Subject: Re: Help speeding up delete
In-Reply-To: <4162.1132011763@sss.pgh.pa.us>
* 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