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: Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Dilip Kumar <dilipbalaut@gmail.com>, a.kozhemyakin@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Date: 2025-06-10T22:39:51Z
Lists: pgsql-bugs
On Tue, Jun 10, 2025 at 08:14:40PM +0900, Michael Paquier wrote: > Hmm. I am wondering whether this would be enough; these are not the > only places where we use select_no_parens and select_with_parens. I'd > be curious to see what you think a fully-bloomed fix should look like. By the way, this report also means that none of the problematic query patterns are run in the main regression test suite, or we would have noticed something immediately when running the recovery test 027_stream_regress.pl that loads PGSS. So we have a problem in test coverage with query normalization patterns. But we also have a second, older, problem in terms of coverage regarding the parentheses patterns that are assumed as supported in the parser. Even if we finish by reverting the nested query tracking support for now (let's settle things before beta2 not after it), we should definitely improve the main regression test suite in this area to make sure that reintroducing it safe. -- 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