Re: Very poor performance loading 100M of sql data using

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 im****ting 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 im****ted, load the data 
into it, then add the check constraints, indexes, and modify the 
rules/triggers to handle the inserts to the parent table.



-- 

Shane Ambler
pgSQL (at) Sheeky (dot) Biz

Get Sheeky @[EMAIL PROTECTED]
 http://Sheeky.Biz

-- 
Sent via pgsql-performance mailing list (pgsql-performance@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance