From: Dave Dutcher <dave@tridecap.com>
To: gry@ll.mit.edu
To: pgsql-performance@postgresql.org
Subject: Re: simple join uses indexes, very slow
Date: Tue, 28 Mar 2006 10:18:25 -0600
Message-ID: <00c901c65283$401f14d0$8300a8c0@tridecap.com> (raw)
In-Reply-To: <20060327134733.72422d23.gry@ll.mit.edu>
> -----Original Message-----
> From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-
> owner@postgresql.org] On Behalf Of george young
> Sent: Monday, March 27, 2006 12:48 PM
> To: pgsql-performance@postgresql.org
> Subject: [PERFORM] simple join uses indexes, very slow
>
[Snip]
>
> Indexes:
> "parameters_idx" btree (run, opset_num, step_num, opset,
opset_ver,
> step, step_ver, name, split, wafers)
> "parameters_opset_idx" btree (opset, step, name)
> "parameters_step_idx" btree (step, name)
>
Have you tried creating some different indexes on parameters? I don't
know if it should matter or not, but I would try some indexes like:
(run, opset_num) //Without all the other columns
(opset_num, run) //Backwards
(opset_num)
I don't really know Postgres internals all that well. It just seems to
me that parameters_idx has a lot of columns this query is not interested
in. I'd just be curious to see what happens.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dave@tridecap.com, gry@ll.mit.edu
Subject: Re: simple join uses indexes, very slow
In-Reply-To: <00c901c65283$401f14d0$8300a8c0@tridecap.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox