Re: BUG #19082: Failing assert in index scan

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Matthijs van der Vleuten <postgresql@zr40.nl>

Cc: pgsql-bugs@lists.postgresql.org

Date: 2025-10-10T16:28:37Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Remove overzealous _bt_killitems assertion.
- 843e50208a31 19 (unreleased) landed
- 61de81a496dc 18.1 landed
- ae15cebc2035 17.7 landed
- c160fd46910e 16.11 landed
- ca0c9390865d 15.15 landed
- 314004021e54 14.20 landed
- af302ff6b84a 13.23 landed
Make _bt_killitems drop pins it acquired itself.
- c7f25feb3862 16.10 cited

On Fri, Oct 10, 2025 at 12:13 PM Matthijs van der Vleuten
<postgresql@zr40.nl> wrote:
> No, none of the tables and indexes in that database are unlogged or temporary.

Are these backwards scans? In other words, does EXPLAIN show "Index
Scan Backwards" for these queries? I see that the first query "ORDER
BY "mentions"."id" ASC", but perhaps that index column is declared as
DESC (in which case it'd be a backwards scan)?

-- 
Peter Geoghegan