Re: PostgreSQL opens all the indexes of a relation for every Queryduring Planning Time?

Поиск
Список
Период
Сортировка
От Meenatchi Sandanam
Тема Re: PostgreSQL opens all the indexes of a relation for every Queryduring Planning Time?
Дата
Msg-id CAJJu9dN=omj9r_eAWUNPP2zKMXSduVcjisbDoX=PuVuGCRfwpQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PostgreSQL opens all the indexes of a relation for every Queryduring Planning Time?  (Jason Petersen <jason@citusdata.com>)
Список pgsql-hackers
Дерево обсуждения

On Fri, Mar 16, 2018 at 10:48 PM, Jason Petersen <jason@citusdata.com> wrote:
On Mar 15, 2018, at 4:18 AM, Meenatchi Sandanam <meen.opm@gmail.com> wrote:

On checking PostgreSQL code, we see it opens all indexes of a relation for every query planning time as in the attachment. If that is the case, it might lead to Performance degradation for relations with many indexes. Is there any other better way to handle this like Scanning/Opening only the indexes related to columns specified in the query?

I’d think you’d need a pretty clear profiling run that points to this as a hot spot before deciding to optimize it. Do you have a query where this is the case?

--
Jason Petersen
Software Engineer | Citus Data
303.736.9255


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: [HACKERS] Add support for tuple routing to foreign partitions
Следующее
От: Pavel Stehule
Дата:
Сообщение: possibly to automatic detection of bad variable types in plans?