Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw)

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw)
Дата
Msg-id CAMkU=1xTHcVOpSZU2zbdUv32xwhNOdurQ5tjO9=GXPLmGheGew@mail.gmail.com
обсуждение исходный текст
Ответ на PostgreSQL optimizer use seq scan instead of pkey index only scan (inqueries with postgres_fdw)  (Vitaly Baranovsky <barvetalforums@gmail.com>)
Ответы Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw)  (Vitaly Baranovsky <barvetalforums@gmail.com>)
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-performance
Дерево обсуждения
On Mon, May 6, 2019 at 10:44 AM Vitaly Baranovsky <barvetalforums@gmail.com> wrote:
Hello all,

I faced strange behavior of PostgreSQL during the query execution.

 ...
 
Also, please, note, that SQL without WHERE clause has been set to the foreign server:
"              Remote SQL: SELECT primary_uuid FROM public.foreign_table"

So, the optimizer doesn't select optimal plans for such executions :(

It works the way you want in version 12, which is currently under development and should be released in 5 months or so.

Cheers,

Jeff

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

Предыдущее
От: Vitaly Baranovsky
Дата:
Сообщение: PostgreSQL optimizer use seq scan instead of pkey index only scan (inqueries with postgres_fdw)
Следующее
От: Vitaly Baranovsky
Дата:
Сообщение: Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw)