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

From Tom Lane
Subject Re: get_actual_variable_range vs idx_scan/idx_tup_fetch, again
Date
Msg-id 12326.1520262537@sss.pgh.pa.us
Whole thread Raw
In response to get_actual_variable_range vs idx_scan/idx_tup_fetch, again  (Marko Tiikkaja <marko@joh.to>)
Responses Re: get_actual_variable_range vs idx_scan/idx_tup_fetch, again
List pgsql-hackers
Marko Tiikkaja <marko@joh.to> writes:
> So I'm in the same pickle again.  According to pg_stat_user_indexes an
> index is being used all the time.  However, it's only being used by
> mergejoinscansel() to compare these two plans:

If it's not being used otherwise, could you drop it?

> I think it would be really important to have a way to turn off
> get_actual_variable_range() for a specific index during runtime.  Would a C
> level hook be acceptable for this?

You haven't really made a case for why you (or anyone else) should care.
As long as the planner makes the right choice, having investigated a wrong
choice doesn't seem like a bug to me.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PATCH: psql tab completion for SELECT
Next
From: Claudio Freire
Date:
Subject: Re: [HACKERS] [PATCH] Vacuum: Update FSM more frequently