Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: a.kozhemyakin@postgrespro.ru, pgsql-bugs@lists.postgresql.org, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Date: 2025-06-08T02:39:44Z
Lists: pgsql-bugs
On Sat, Jun 07, 2025 at 10:19:53PM +0530, Dilip Kumar wrote: > I didn't get time to debug, I might look into it tomorrow if someone > doesn't do it before that, but I am able to reproduce the issue and > seems like problem is with respect to computing the quer_loc in below > loop, and due to that 'quer_loc' is becoming bigger than query_len and > hitting the assert. The loop in charge of assigning the constants in the queries needs to be smarter in terms of the new locations assigned to sub-queries, here the VALUES one. 499edb09741b is the origin of the regression, so open item assigned to me (will look into it later), adding Anthonin in CC. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Revert support for improved tracking of nested queries
- f85f6ab051b7 18.0 landed
-
psql: fix order of join clauses when listing extensions
- 112e40b867b3 18.0 cited