Fw: Re: Bitmap scan seem like such a strange choice when "limit 1"

From: Klaudie Willis <Klaudie(dot)Willis(at)protonmail(dot)com>
To: PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Fw: Re: Bitmap scan seem like such a strange choice when "limit 1"
Date: 2020-09-07 07:06:53
Message-ID: gaWaPH2J0kYNq2ZfeVlM2R5JjFSPrXYeo8P8l23JGaL8z9WxfmbVWSMBPlvOPh0jlskix5fnxruBpDNKAjLax_VoWZE7TZQ7pHxBPkRHw3E=@protonmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, September 7, 2020 9:04 AM, Klaudie Willis <Klaudie(dot)Willis(at)protonmail(dot)com> wrote:

> Maybe the right way to improve this is to bypass add_paths_to_append_rel
> entirely when there's exactly one surviving child rel, and make it
> just use all the surviving paths for that child.
> regards, tom lane

Does this classify as a bug, or is it "by design"? Should I submit one for PG13beta3? To me, this seems like quite a straight forward case. Big database partitioned, two key lookups, both indexed where one key isolates a partition, and with a limit constraint. Yet it chooses a plan that is 1000x slower than the optimal plan.

K

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Klaudie Willis 2020-09-07 07:09:42 Fw: Re: Bitmap scan seem like such a strange choice when "limit 1"
Previous Message Magnus Hagander 2020-09-06 17:27:43 Re: Fix typo in Comments of HandleProcSignalBarrierInterrupt