Postgres Pro
Downloads
Home   >   mailing lists

Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw) - Mailing list pgsql-performance

From Jeff Janes
Subject Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw)
Date
Msg-id CAMkU=1xTHcVOpSZU2zbdUv32xwhNOdurQ5tjO9=GXPLmGheGew@mail.gmail.com
Whole thread Raw
In response to PostgreSQL optimizer use seq scan instead of pkey index only scan (inqueries with postgres_fdw)  (Vitaly Baranovsky <barvetalforums@gmail.com>)
Responses 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>)
List pgsql-performance
Tree view
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 by date:

Previous
From: Vitaly Baranovsky
Date:
Subject: PostgreSQL optimizer use seq scan instead of pkey index only scan (inqueries with postgres_fdw)
Next
From: Vitaly Baranovsky
Date:
Subject: Re: PostgreSQL optimizer use seq scan instead of pkey index only scan(in queries with postgres_fdw)