Re: More correlated (?) index woes

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: bricklen <bricklen(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: More correlated (?) index woes
Date: 2016-03-31 10:21:21
Message-ID: CAEzk6ffDp9VDqSZo-zkijk2G1Kp+Lx1n5oeViHMmF0BDLv_Uhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 31 Mar 2016 03:02, "bricklen" <bricklen(at)gmail(dot)com> wrote:
> Perhaps a partial index like "create index pa_sc_id_pidx on pa (sc_id) with (fillfactor=100) where field1 IS NULL;" will help?

Thanks for the suggestion.

It might, but the problem with that is there's (something like)
field2-16 which are used in similar queries.

I'll stick with enable_seqscan=off, it seems to be doing the trick;
thanks though.

Geoff

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Pavlov, Vladimir 2016-03-31 10:25:41 Re: Multixacts wraparound monitoring
Previous Message margrit drescher 2016-03-31 09:53:26 Re: Postgres 9.4.4/9.4.6: plpython2/3 intallation issues on a Windows 7 machine