X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5E0B7D1B47D for ; Fri, 6 Feb 2004 14:50:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 25098-09 for ; Fri, 6 Feb 2004 10:50:48 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id F05ECD1D2A0 for ; Fri, 6 Feb 2004 10:50:43 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i16EofUR029494; Fri, 6 Feb 2004 09:50:42 -0500 (EST) To: Steve Lane Cc: pgsql-admin@postgresql.org Subject: Re: Index (re)-creation speed In-reply-to: References: Comments: In-reply-to Steve Lane message dated "Fri, 06 Feb 2004 01:03:48 -0600" Date: Fri, 06 Feb 2004 09:50:41 -0500 Message-ID: <29493.1076079041@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/76 X-Sequence-Number: 12250 Steve Lane writes: > And still, none of this explains to me why the index on id_item drove the > COPY cost up so apparently dramatically. I tried the COPY again both with > and without that one index and in both cases it caused COPY to go from 5 to > 40+ seconds. That doesn't make a lot of sense to me either, particularly seeing that id_item seems to be an intermediate case as far as uniqueness goes. Do you still get 30+ seconds to COPY if that is the *only* index? If the data you're using isn't too sensitive, would you mind sending me a copy (off-list)? I'm interested to try profiling this behavior. regards, tom lane