Re: Force specific index disuse

From: Oleg Bartunov <obartunov(at)gmail(dot)com>
To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Force specific index disuse
Date: 2014-05-21 09:36:00
Message-ID: CAF4Au4y93AV2dKuQ2ABJbsMRT_E1nUTz_+pipHiFZuA25_1iFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We routinely use plantuner. http://www.sai.msu.su/~megera/wiki/plantuner

On Tue, May 20, 2014 at 12:38 PM, Steve Crawford
<scrawford(at)pinpointresearch(dot)com> wrote:
> Is there a way to force a specific index to be removed from consideration in
> planning a single query?
>
> Specifically, on a 60-million-row table I have an index that is a candidate
> for removal. I have identified the sets of nightly queries that use the
> index but before dropping it I would like to run EXPLAIN and do timing tests
> on the queries to see the impact of not having that index available and
> rewrite the query to efficiently use other indexes if necessary.
>
> Cheers,
> Steve
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Khangelani Gama 2014-05-21 09:54:39 Need help on triggers - postgres 9.1.2
Previous Message John R Pierce 2014-05-21 04:28:07 Re: Convert an XML database