X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id AF4CDD1C4B7 for ; Mon, 21 Jul 2003 05:09:09 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 22111-02 for ; Mon, 21 Jul 2003 05:09:07 +0000 (GMT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 1226BD1C510 for ; Mon, 21 Jul 2003 02:09:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h6L592Q3027642; Mon, 21 Jul 2003 01:09:02 -0400 (EDT) To: jeremy.guthrie@berbee.com Cc: pgsql-performance@postgresql.org Subject: Re: Poor delete performance AFTER vacuum analyze In-reply-to: <200307201851.39756.jeremy.guthrie@berbee.com> References: <200307191622.46709.jeremy.guthrie@berbee.com> <19929.1058676291@sss.pgh.pa.us> <200307201851.39756.jeremy.guthrie@berbee.com> Comments: In-reply-to "Jeremy M. Guthrie" message dated "Sun, 20 Jul 2003 18:51:39 -0500" Date: Mon, 21 Jul 2003 01:09:02 -0400 Message-ID: <27641.1058764142@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/317 X-Sequence-Number: 2610 "Jeremy M. Guthrie" writes: > I looked back at my code and I also need to reclarify something. The delete > at the end is multiple delete statements within a transaction. I think you are going to have to show us all the details of what you're doing in between these queries. I was expecting to see a difference in query plans, but you've got the exact same plan in all three runs --- so it's not the planner making the difference here, nor the ANALYZE statistics. My best conjecture now is something odd about the way you are deleting the old data or loading the new. regards, tom lane