Re: Weird seqscan node plan

27.11.2019, 15:42, "Andrei Zhidenkov" : > At this point I disagree. It’s faster to fetch one row using seq scan that > using index scan as well as fetching number of consecutive rows is faster via > seq scan. Index scan is not always faster. > Yes, you are right in common: Index scan is not a

Re: Weird seqscan node plan

At this point I disagree. It’s faster to fetch one row using seq scan that using index scan as well as fetching number of consecutive rows is faster via seq scan. Index scan is not always faster. > On 27. Nov 2019, at 04:53, Игорь Выскорко wrote: > > Why planner mistakes in determining the num

Re: Weird seqscan node plan

> > Try increasing the following parameters to 14 (or even 16, if you are not > sure about number of tables involved): > > geqo_threshold = 14 > > from_collapse_limit = 14 > > join_collapse_limit = 14 > > “about 12” is too close to default limit, 12. > > Regards, > > Igor Neyman Hi Igor, Is "

RE: Weird seqscan node plan

From: Игорь Выскорко [mailto:vyskorko.i...@yandex.ru] Sent: Tuesday, November 26, 2019 4:13 AM To: Andrei Zhidenkov Cc: pgsql-general@lists.postgresql.org Subject: Re: Weird seqscan node plan 26.11.2019, 16:02, "Andrei Zhidenkov" mailto:andrei.zhiden...@n26.com>>: How many table

Re: Weird seqscan node plan

  26.11.2019, 16:02, "Andrei Zhidenkov" :How many tables do you have in your query? If too many, in your case “Genetic Query Optiomiation” might be used (https://www.postgresql.org/docs/10/geqo-pg-intro.html). On 26. Nov 2019, at 03:19, Игорь Выскорко wrote: Hi all!I'm con

Re: Weird seqscan node plan

How many tables do you have in your query? If too many, in your case “Genetic Query Optiomiation” might be used (https://www.postgresql.org/docs/10/geqo-pg-intro.html ). > On 26. Nov 2019, at 03:19, Игорь Выскорко wrote: > > Hi all! > I'm