Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0EMw8V42481 for ; Mon, 14 Jan 2002 17:58:08 -0500 (EST) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.4/8.11.4) id g0EMlfn08427 for pgsql-sql@postgresql.org; Mon, 14 Jan 2002 17:47:41 -0500 (EST) (envelope-from news) From: Jochem van Dieten X-Newsgroups: comp.databases.postgresql.sql Subject: Re: Long-running DELETE...WHERE... Date: Mon, 14 Jan 2002 23:47:37 +0100 Organization: OnLine Internet Lines: 13 Message-ID: <3C436009.40204@dev.null> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.tudelft.nl User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.7+) Gecko/20020107 X-Accept-Language: en-us To: pgsql-sql@postgresql.org X-Archive-Number: 200201/222 X-Sequence-Number: 6306 Jeff Boes wrote: > Why would a delete involving a subselect run so much longer than the > individual delete commands? Some SQL statements are faster than others. Try to rewrite your query to use EXISTS instead of IN and see if it makes any difference. I would recommend using EXPLAIN to find out what PostgreSQL is really doing and optimize from there. jochem