Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id D1904476DFB for ; Thu, 13 Jun 2002 09:58:54 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 7FFC0476C98 for ; Thu, 13 Jun 2002 09:52:37 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g5DDqVb19017; Thu, 13 Jun 2002 09:52:31 -0400 (EDT) To: terry@greatgulfhomes.com Cc: "Postgres (E-mail)" Subject: Re: COPY optimization issue In-reply-to: <003901c212dc$627a9120$2766f30a@development.greatgulfhomes.com> References: <003901c212dc$627a9120$2766f30a@development.greatgulfhomes.com> Comments: In-reply-to terry@greatgulfhomes.com message dated "Thu, 13 Jun 2002 09:15:26 -0400" Date: Thu, 13 Jun 2002 09:52:30 -0400 Message-ID: <19014.1023976350@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200206/17 X-Sequence-Number: 1392 terry@greatgulfhomes.com writes: > I currently just use the COPY command, but with over 800,000 records, this > takes quite some time. > Is there a faster way? Drop and recreate indexes might help. See http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/populate.html regards, tom lane