Re: postgresql 10.1 wrong plan in when using partitions bug

Поиск
Список
Период
Сортировка
От Mariel Cherkassky
Тема Re: postgresql 10.1 wrong plan in when using partitions bug
Дата
Msg-id CA+t6e1=yXX0JvMTCs6+fjQiZ8VDf5bTgYqBxtwx_bLWW+S+YtQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: postgresql 10.1 wrong plan in when using partitions bug  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-performance
Дерево обсуждения
Hi Tom,
Did you hear about any solution that is similar to oracle`s global index ? Is there any way to query all the partitions with one index? 

2018-02-04 17:39 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
Mariel Cherkassky <mariel.cherkassky@gmail.com> writes:
> Great, it solved the issue. Seems problematic that the planner do full
> scans on all partitions in the first case isnt it ? Seems like a bug ?

to_date isn't an immutable function (it depends on timezone and possibly
some other GUC settings).  So there's a limited amount that the planner
can do with it.

                        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: postgresql 10.1 wrong plan in when using partitions bug
Следующее
От: Rick Otten
Дата:
Сообщение: Re: postgresql 10.1 wrong plan in when using partitions bug