Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: Manuel Reyes Bravo <manuelreyesbravo(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
Date: 2026-08-24 18:19:54
Message-ID: CAB8bMisGzpx1TJCqEruff9tcjCPpRMq-HP55N+bcEQNfSNzQVw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

пн, 24 авг. 2026 г. в 21:51, Manuel Reyes Bravo <manuelreyesbravo(at)gmail(dot)com
>:

>
> The attached tarball includes that script as alcance.sql.
>
> In the future, it would be better to attach patches rather than archives.
I kept the fix minimal: one guard after bms_is_subset() in
check_index_only(), rejecting the plan when no key column is returnable.

--
Regards,
Rachitskiy Andrey

Attachment Content-Type Size
0002-Reject-index-only-scans-when-index-cannot-return.patch text/x-patch 1.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Manuel Reyes Bravo 2026-08-24 18:52:42 Re: BUG #19638: Planner chooses an index-only scan for an index AM without amcanreturn, and execution fails
Previous Message Manuel Reyes Bravo 2026-08-24 17:01:57 Re: BUG #19639: EXPLAIN (FORMAT JSON) emits a 309-digit cost value, and the node still reports "Disabled": false