From: "Joel Fradkin" <jfradkin@wazagua.com>
To: "'Merlin Moncure'" <merlin.moncure@rcsonline.com>,
	"'Matthew Sackman'" <matthew@lshift.net>
Cc: <pgsql-performance@postgresql.org>
Subject: Re: Massive performance issues
Date: Thu, 1 Sep 2005 14:42:51 -0400
Message-ID: <003901c5af24$f5cd8ee0$797ba8c0@jfradkin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3417DD25A@Herge.rcsinc.local>

Any chance it's a vacuum thing?
Or configuration (out of the box it needs adjusting)?

Joel Fradkin
 
 

-----Original Message-----
From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Merlin Moncure
Sent: Thursday, September 01, 2005 2:11 PM
To: Matthew Sackman
Cc: pgsql-performance@postgresql.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