John Rouillard wrote:
> We can't do this as we are backfilling a couple of months of data
> into tables with existing data.
Is this a one off data loading of historic data or an ongoing thing?
>>> The only indexes we have to drop are the ones on the primary keys
>>> (there is one non-primary key index in the database as well).
If this amount of data importing is ongoing then one thought I would try
is partitioning (this could be worthwhile anyway with the amount of data
you appear to have).
Create an inherited table for the month being imported, load the data
into it, then add the check constraints, indexes, and modify the
rules/triggers to handle the inserts to the parent table.
pgSQL (at) Sheeky (dot) Biz
Get Sheeky @ http://Sheeky.Biz
In response to
pgsql-performance by date
|Next:||From: Tino Wildenhain||Date: 2008-04-28 19:59:02|
|Subject: Re: Best practice to load a huge table from ORACLE to PG|
|Previous:||From: Gregory Stark||Date: 2008-04-28 18:40:25|
|Subject: Re: Benchmarks WAS: Sun Talks about MySQL|