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-12 09:15:11
Message-ID: 178920451166.1175.1908642259509647383.pgcf@coridan.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hello,

I think that the that SQLSTATE chosen in unicode_assigned() is wrong: this not a SQL statement syntax error but more a feature not supported for the current database encoding;
ERRCODE_FEATURE_NOT_SUPPORTED is more appropriate.

Maybe you could add a regression test for tid.c ?

Other modifications look good to me and more difficult to test automatically.

Regards,
PF

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2026-09-12 13:57:18 Re: BUG #19633: Unexpected results of IN (subquery) with a non-deterministic collation
Previous Message PG Bug reporting form 2026-09-11 20:00:01 BUG #19684: Assertion in tuplesort_begin_heap() falsified by parallel plan with sort

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2026-09-12 10:34:21 Re: SSI: ON CONFLICT DO SELECT takes no predicate lock on the returned row
Previous Message Jeevan Chalke 2026-09-12 06:06:11 Re: Add PRODUCT() aggregate function