From: | "Joel Fradkin" <jfradkin(at)wazagua(dot)com> |
---|---|
To: | "'Merlin Moncure'" <merlin(dot)moncure(at)rcsonline(dot)com>, "'Matthew Sackman'" <matthew(at)lshift(dot)net> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Massive performance issues |
Date: | 2005-09-01 18:42:51 |
Message-ID: | 003901c5af24$f5cd8ee0$797ba8c0@jfradkin |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Any chance it's a vacuum thing?
Or configuration (out of the box it needs adjusting)?
Joel Fradkin
-----Original Message-----
From: pgsql-performance-owner(at)postgresql(dot)org
[mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of Merlin Moncure
Sent: Thursday, September 01, 2005 2:11 PM
To: Matthew Sackman
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Massive performance issues
> I'm having performance issues with a table consisting of 2,043,133
rows.
> The
> schema is:
> locality_1 has 16650 distinct values and locality_2 has 1156 distinct
> values.
Just so you know I have a 2GHz p4 workstation with similar size (2M
rows), several keys, and can find and fetch 2k rows based on 20k unique
value key in about 60 ms. (.06 seconds).
Merlin
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-01 18:47:06 | Re: Massive performance issues |
Previous Message | Merlin Moncure | 2005-09-01 18:10:31 | Re: Massive performance issues |