X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 98DF1D1B513 for ; Fri, 26 Sep 2003 14:20:34 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 22316-04 for ; Fri, 26 Sep 2003 11:20:06 -0300 (ADT) Received: from lakemtao02.cox.net (lakemtao02.cox.net [68.1.17.243]) by svr1.postgresql.org (Postfix) with ESMTP id 31B03D1B509 for ; Fri, 26 Sep 2003 11:20:02 -0300 (ADT) Received: from lhosts ([68.11.66.83]) by lakemtao01.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20030926123736.VWNM29208.lakemtao01.cox.net@lhosts> for ; Fri, 26 Sep 2003 08:37:36 -0400 Subject: Re: populate table with large csv file From: Ron Johnson To: PgSQL General ML In-Reply-To: References: Content-Type: text/plain Message-Id: <1064579855.26936.57.camel@haggis> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 26 Sep 2003 07:37:35 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/1671 X-Sequence-Number: 49890 On Fri, 2003-09-26 at 06:58, Dave [Hawk-Systems] wrote: [snip] > Unfortunately processing the 143mb file which would result in a database size of > approx 500mb takes an eternity. As luck would have it we can get away with just Something's not right, then. I loaded 30GB in about 8 hours, on a slow system, with non-optimized IO. Did you drop the indexes first? -- ----------------------------------------------------------------- Ron Johnson, Jr. ron.l.johnson@cox.net Jefferson, LA USA "As the night fall does not come at once, neither does oppression. It is in such twilight that we must all be aware of change in the air - however slight - lest we become unwitting victims of the darkness." Justice William O. Douglas