Re: Unused index influencing sequential scan plan - Mailing list pgsql-performance

From Peter Geoghegan
Subject Re: Unused index influencing sequential scan plan
Date
Msg-id CAEYLb_UD3jmHyCTnfrfywcNG5A4aSt9X8X+9TTVojdxgW4Asnw@mail.gmail.com
Whole thread Raw
In response to Re: Unused index influencing sequential scan plan  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unused index influencing sequential scan plan
Re: Unused index influencing sequential scan plan
List pgsql-performance
On 18 October 2012 17:52, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I forgot to mention that there is a klugy workaround: add the required
> variable(s) as extra index columns.  That is,
>
>         create index i on t (foo(x), x);

Is there a case to be made for a index access method whose
pseudo-indexes costs essentially nothing to maintain, and simply
represent an ongoing obligation for ANALYZE to provide statistics for
an expression?

--
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unused index influencing sequential scan plan
Next
From: Thom Brown
Date:
Subject: Re: Unused index influencing sequential scan plan