Re: Bug: Very poor query optimization by Postgres

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tobias Völk <tobias(dot)voelk(at)t-online(dot)de>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Bug: Very poor query optimization by Postgres
Date: 2020-07-07 20:19:55
Message-ID: CAKFQuwYynrrWXmK52a5p01PdYyrAUswUY7O2KxrVbosF=ssw2g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, July 7, 2020, Tobias Völk <tobias(dot)voelk(at)t-online(dot)de> wrote:
>
> that Postgres is performing a sequential scan with 2 workers instead of
> just returning the number or rows!
>
https://wiki.postgresql.org/wiki/Index-only_scans

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Soumyadeep Chakraborty 2020-07-08 00:37:17 Re: posgres 12 bug (partitioned table)
Previous Message PG Bug reporting form 2020-07-07 18:48:30 BUG #16529: Installation error/bug