| From: | "Brett W(dot) McCoy" <bmccoy(at)lan2wan(dot)com> |
|---|---|
| To: | Jason Slagle <raistlin(at)tacorp(dot)net> |
| Cc: | Tim Perdue <perdue(at)raccoon(dot)com>, "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>, pgsql-sql(at)hub(dot)org |
| Subject: | Re: [SQL] Performance |
| Date: | 1999-03-10 03:44:21 |
| Message-ID: | Pine.LNX.4.04.9903092242290.18400-100000@dragosani.lan2wan.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Tue, 9 Mar 1999, Jason Slagle wrote:
> What, if anything, are you using as an index.
>
> I have 1,400,000 entries (200MB) I'm inserting into a database. Radius
> detail files as a matter of fact. Apart from COPY taking forever to load
> that (probably due to my several indexes), it seems the select is VERY
> slow. Any tips?
I found that if you create an index before doing a bulk COPY, yes, it does
take forever to load, and the select is slow. What I did was drop the
indices built from the COPY and rebuild them. Speeded the selects up
significantly. So now I don't build any indices until after I load my
huge databases in.
Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
That's what she said.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s:-- a C++++ UL++++$ P+ L+++ E W++ N+ o K- w--- O@ M@ !V PS+++
PE Y+ PGP- t++ 5- X+ R+@ tv b+++ DI+++ D+ G++ e>++ h+(---) r++ y++++
------END GEEK CODE BLOCK------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Remigiusz Sokolowski | 1999-03-10 13:13:45 | shared tables |
| Previous Message | Tim Perdue | 1999-03-10 03:33:57 | Re: [SQL] Performance |