Re: get_actual_variable_range vs idx_scan/idx_tup_fetch - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: get_actual_variable_range vs idx_scan/idx_tup_fetch
Date
Msg-id 54427B6D.80306@joh.to
Whole thread Raw
In response to Re: get_actual_variable_range vs idx_scan/idx_tup_fetch  (Bruce Momjian <bruce@momjian.us>)
Responses Re: get_actual_variable_range vs idx_scan/idx_tup_fetch
Re: get_actual_variable_range vs idx_scan/idx_tup_fetch
List pgsql-hackers
On 10/18/14, 4:33 PM, Bruce Momjian wrote:
> On Sat, Oct 18, 2014 at 04:29:41PM +0200, Marko Tiikkaja wrote:
>> Another idea had was some way to tell the optimizer not to use that
>> particular index for stats lookups, but probably the use case for
>> such a feature would be a bit narrow.
>
> Well, if the index is there, why not use it?  I thought the problem was
> just that you had no visibility into how those statistics were being
> accessed.

Yes, exactly; if I had had the option to disable the index from the 
optimizer's point of view, I'd have seen that it's not used for looking 
up any data by any queries, and thus I would have known that I can 
safely drop it without slowing down queries.  Which was the only thing I 
cared about, and where the stats we provide failed me.


.marko



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Hash index creation warning
Next
From: Thomas Kellerer
Date:
Subject: Re: Materialized views don't show up in information_schema