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

Ough, I believed I had use_remote_estimate = true in my database, but it was false :( With use_remote_estimate = true everything works well! Here is explain analyze with use_remote_estimate = true: "Nested Loop (cost=100.45..108.97 rows=10 width=16) (actual time=1.037..1.037 rows=0

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

instead of pk key index only scan for the local table? Thank you ᐧ On Mon, May 6, 2019 at 6:32 PM Jeff Janes wrote: > On Mon, May 6, 2019 at 10:44 AM Vitaly Baranovsky < > barvetalfor...@gmail.com> wrote: > >> Hello all, >> >> I faced strange behavior of Post