Re: Importing Large Amounts of Data
Curt Sampson <cjs@cynic.net>
From: Curt Sampson <cjs@cynic.net>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Christopher Kings-Lynne <chriskl@familyhealth.com.au>, <pgsql-hackers@postgresql.org>
Date: 2002-04-16T01:53:49Z
Lists: pgsql-hackers
On Mon, 15 Apr 2002, Bruce Momjian wrote:
> Can you check your load and see if there is a PRIMARY key on the table
> at the time it is being loaded.
There is not. I create the table with a PRIMARY KEY declaration,
but I drop that index before doing the import, and do an ALTER
TABLE to re-add the primary key afterwards.
At one point I tried doing a load with all indices enabled, but
after about eight or nine hours I gave up. (Typically the load
takes about 30 minutes. This is using about 2% of the sample data.)
> In the old days, we created indexes
> only after the data was loaded, but when we added PRIMARY key, pg_dump
> was creating the table with PRIMARY key then loading it, meaning the
> table was being loaded while it had an existing index. I know we fixed
> this recently but I am not sure if it was in 7.2 or not.
Ah, I saw that fix. But I'm doing the load by hand, not using
pg_restore.
cjs
--
Curt Sampson <cjs@cynic.net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC