Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 921249FB1D2 for ; Thu, 5 Oct 2006 10:20:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 31453-06 for ; Thu, 5 Oct 2006 13:20:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 9C1389F9F77 for ; Thu, 5 Oct 2006 10:20:00 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k95DJO2n012201; Thu, 5 Oct 2006 09:19:45 -0400 (EDT) To: Steve Peterson cc: me@alternize.com, pgsql-performance@postgresql.org Subject: Re: UPDATE becomes mired / win32 In-reply-to: <6.2.3.4.0.20061005000508.04bb03d8@localhost> References: <6.2.3.4.0.20061004094635.03c114a8@localhost> <0d3301c6e7e0$ce71c190$6501a8c0@iwing> <6.2.3.4.0.20061005000508.04bb03d8@localhost> Comments: In-reply-to Steve Peterson message dated "Thu, 05 Oct 2006 00:06:49 -0500" Date: Thu, 05 Oct 2006 09:19:24 -0400 Message-ID: <12200.1160054364@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/124 X-Sequence-Number: 21253 Steve Peterson writes: > The behavior also persists across a dump/reload of the table into a > new install on a different machine. IIRC dump/reload rebuilds > indexes from scratch. Hm. There must be something you're not telling us that accounts for the difference between the original table and the copied version --- foreign keys linking from other tables, perhaps? regards, tom lane