Re: More correlated (?) index woes - Mailing list pgsql-general

From bricklen
Subject Re: More correlated (?) index woes
Date
Msg-id CAGrpgQ8zau=VpUfw48Qkkdvc_8jf-E52aZq3DeFS2KVnQWm6pw@mail.gmail.com
Whole thread Raw
In response to Re: More correlated (?) index woes  (Geoff Winkless <pgsqladmin@geoff.dj>)
Responses Re: More correlated (?) index woes  (Geoff Winkless <pgsqladmin@geoff.dj>)
List pgsql-general

On Tue, Mar 29, 2016 at 3:47 AM, Geoff Winkless <pgsqladmin@geoff.dj> wrote:
On 28 March 2016 at 20:23, I wrote:
Table pa has 7522676 rows, 4834042 of which have field1 NULL, so it's absolutely not reasonable to expect this to be an optimal strategy.
It occurred to me that even though the majority of values are NULL, there are ​
 
​1691 unique values in pa.field1, so I suppose it might seem more attractive to the planner than it should do (that's more unique values than there are scdate entries).


Perhaps a partial index like "create index pa_sc_id_pidx on pa (sc_id) with (fillfactor=100) where field1 IS NULL;" will help?

pgsql-general by date:

Previous
From: Slava Bendersky
Date:
Subject: bdr replication
Next
From: Craig Ringer
Date:
Subject: Re: bdr replication