Re: [SQL] Optimizing huge inserts/copy's

[Tom Lane]

Webb Sprague <[EMAIL PROTECTED]> writes:
> I am experimenting with this too.  If I have any
> indexes at all, the copy's get VERY SLOW as the table
> gets big.  Delete ALL your indexes, do your copy's,
> and then create your indexes again.

Do you have a lot of equal index keys in the data you're inserting?
I've recently been swatting some performance problems in the btree
index code for the case of large numbers of equal keys.

                        regards, tom lane