Re: Optimizing huge inserts/copy's

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Webb Sprague <wsprague100(at)yahoo(dot)com>
Cc: Jie Liang <jliang(at)ipinc(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Optimizing huge inserts/copy's
Date: 2000-08-30 20:22:49
Message-ID: 21902.967666969@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Webb Sprague <wsprague100(at)yahoo(dot)com> 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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message pyz 2000-08-30 21:03:29 7.0.2 questions on encoding and compilation
Previous Message Stephan Szabo 2000-08-30 20:06:46 Re: Optimizing huge inserts/copy's