From: Bruno Wolff III <bruno@wolff.to>
To: Ed L. <pgsql@bluepolka.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORMANCE] slow small delete on large table
Date: Mon, 23 Feb 2004 21:00:17 -0600
Message-ID: <20040224030017.GA2872@wolff.to> (raw)
In-Reply-To: <200402231910.57078.pgsql@bluepolka.net>
References: <200402231910.57078.pgsql@bluepolka.net>
On Mon, Feb 23, 2004 at 19:10:57 -0700,
"Ed L." <pgsql@bluepolka.net> wrote:
>
> A 7.3.4 question...
>
> I want to "expire" some data after 90 days, but not delete too
> much at once so as not to overwhelm a system with precariously
> balanced disk I/O and on a table with millions of rows. If I
> could say it the way I think for a simple example, it'd be
> like this:
If there aren't foreign keys into the table from which rows are being
deleted, then a delete shouldn't have a big impact on the system.
If you do the expires frequently, then there won't be as many records
to delete at one time. The other response showed you how to avoid the
sequential scan, which is the other part of the problem.
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: bruno@wolff.to, pgsql@bluepolka.net
Subject: Re: [PERFORMANCE] slow small delete on large table
In-Reply-To: <20040224030017.GA2872@wolff.to>
* 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