Re: Force specific index disuse
От | Oleg Bartunov |
---|---|
Тема | Re: Force specific index disuse |
Дата | |
Msg-id | CAF4Au4y93AV2dKuQ2ABJbsMRT_E1nUTz_+pipHiFZuA25_1iFA@mail.gmail.com обсуждение исходный текст |
Ответ на | Force specific index disuse (Steve Crawford <scrawford@pinpointresearch.com>) |
Список | 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@pinpointresearch.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@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: