Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000

From: Pierre Forstmann <pierre(dot)forstmann(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Subject: Re: BUG #19631: currtid2() on a view with GROUP BY ctid crashes with XX000
Date: 2026-09-14 16:44:40
Message-ID: 178940428010.1127.8843845816823757805.pgcf@coridan.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

The following review has been posted through the commitfest application:
make installcheck-world: tested, passed
Implements feature: tested, passed
Spec compliant: not tested
Documentation: not tested

Hello,

I have reviewed v2 of patch and it looks good to me.

There is no SQL change: no need to test SQL compliance.

I don't think that documentation should be updated.

Regards,
PF.

The new status of this patch is: Ready for Committer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-09-14 19:07:42 Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
Previous Message Peter Eisentraut 2026-09-14 16:03:15 Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build

Browse pgsql-hackers by date

  From Date Subject
Next Message Bryan Green 2026-09-14 17:26:50 Re: [PATCH] Use Boyer-Moore-Horspool for simple LIKE contains patterns
Previous Message Bryan Green 2026-09-14 16:26:30 Re: Do not scan index in right table if condition for left join evaluates to false using columns in left table