From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andreas Pflug <Andreas.Pflug@web.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow query performance on large table
Date: Tue, 04 Mar 2003 12:53:13 -0500
Message-ID: <27569.1046800393@sss.pgh.pa.us> (raw)
In-Reply-To: <3E64D694.9050309@web.de>
References: <000001c2e25c$ad506170$0c64a8c0@paulspc>
<23081.1046790781@sss.pgh.pa.us>
<3E64D694.9050309@web.de>
Andreas Pflug <Andreas.Pflug@web.de> writes:
> "create index ind_meas on measurement (assessment,time)" should perform
> the same as "... primary key(assessment,time)".
Sure.
> Do possibly non-optimal indices (only assessment, only time as Paul
> described earlier) screw up the optimizer, igoring the better option
> usiing the PK?
One would like to think the optimizer will make the right choice. But
using a two-column index just because it's there isn't necessarily the
right choice. The two-column index will certainly be bulkier and more
expensive to scan, so if there's a one-column index that's nearly as
selective, it might be a better choice.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, Andreas.Pflug@web.de
Subject: Re: Slow query performance on large table
In-Reply-To: <27569.1046800393@sss.pgh.pa.us>
References: <000001c2e25c$ad506170$0c64a8c0@paulspc> <23081.1046790781@sss.pgh.pa.us> <3E64D694.9050309@web.de> <27569.1046800393@sss.pgh.pa.us>
* 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