pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: jboes@nexcerpt.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Long-running DELETE...WHERE...
Date: Mon, 14 Jan 2002 20:21:10 -0500
Message-ID: <21141.1011057670@sss.pgh.pa.us> (raw)
In-Reply-To: <d40a65a1.0201141027.6b15bc97@posting.google.com>
References: <d40a65a1.0201141027.6b15bc97@posting.google.com>

jboes@nexcerpt.com (Jeff Boes) writes:
> My situation: table A has 200,000 rows. I've made up a temporary table
> which holds the single-valued primary key for 80,000 rows which I want
> to delete.
>   DELETE FROM a WHERE id IN (select ID from tmp LIMIT 800);
> runs for several minutes.

WHERE ... IN ... is notoriously inefficient.  I'd try

	DELETE FROM aa WHERE id = tmp.id;

which is not standard SQL but should be able to produce a decent plan.

You might find that a VACUUM ANALYZE on both tables beforehand would be
a good idea, too; never-vacuumed temp tables have some default
statistics assumed that are a lot less than 80k rows.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <21141.1011057670@sss.pgh.pa.us>
Permalink:  ../21141.1011057670@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21141.1011057670@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jboes@nexcerpt.com
  Subject: Re: Long-running DELETE...WHERE...
  In-Reply-To: <21141.1011057670@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