Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e7UKN5C32728 for ; Wed, 30 Aug 2000 16:23:05 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id QAA21917; Wed, 30 Aug 2000 16:22:50 -0400 (EDT) To: Webb Sprague cc: Jie Liang , Stephan Szabo , pgsql-sql@postgresql.org Subject: Re: Optimizing huge inserts/copy's In-reply-to: <20000830185717.12822.qmail@web803.mail.yahoo.com> References: <20000830185717.12822.qmail@web803.mail.yahoo.com> Comments: In-reply-to Webb Sprague message dated "Wed, 30 Aug 2000 11:57:17 -0700" Date: Wed, 30 Aug 2000 16:22:49 -0400 Message-ID: <21902.967666969@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/346 Webb Sprague writes: > I am experimenting with this too. If I have any > indexes at all, the copy's get VERY SLOW as the table > gets big. Delete ALL your indexes, do your copy's, > and then create your indexes again. Do you have a lot of equal index keys in the data you're inserting? I've recently been swatting some performance problems in the btree index code for the case of large numbers of equal keys. regards, tom lane