From: Josh Berkus <josh@agliodbs.com>
To: postgres performance list <pgsql-performance@postgresql.org>
Subject: Strange choice of general index over partial index
Date: Fri, 16 Jan 2015 11:30:08 +1300
Message-ID: <54B83F70.7080004@agliodbs.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
This is an obfuscation and mock up, but:
table files (
id serial pk,
filename text not null,
state varchar(20) not null
... 18 more columns
)
index file_state on (state)
(35GB in size)
index file_in_flight_state (state) where state in (
'waiting','assigning', 'processing' )
(600MB in size)
... 10 more indexes
More important facts:
* state = 'done' 95% of the time. thereform the partial index
represents only 5% of the table
* all indexes and the table are very bloated
* server has 128GB RAM
* Version 9.2.
Given this setup, I would expect the planner to *always* choose
file_in_flight_state over file_state for this query:
SELECT id, filename FROM files WHERE state = 'waiting';
... and yet it keeps selecting file_state based on extremely small
changes to the stats. This is important because the same query, using
file_state, is 20X to 50X slower, because that index frequently gets
pushed out of memory.
What am I missing? Or is this potentially a planner bug for costing?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: josh@agliodbs.com
Subject: Re: Strange choice of general index over partial index
In-Reply-To: <54B83F70.7080004@agliodbs.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