pg_overexplain produces invalid JSON with RANGE_TABLE option
SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
From: SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-15T21:35:46Z
Lists: pgsql-hackers
Attachments
- 0001-Fix-pg_overexplain-invalid-JSON-with-RANGE_TABLE.patch (application/octet-stream) patch 0001
Hi Hackers,
It appears that pg_overexplain produces invalid JSON output when
EXPLAIN (FORMAT JSON, RANGE_TABLE) is used. The "Unprunable RTIs" and
"Result RTIs" properties are emitted as key:value pairs directly inside
the "Range Table" JSON array, which is structurally invalid.
Attempted to fix this by moving ExplainCloseGroup() before the two
overexplain_bitmapset()
calls, so the properties are emitted as siblings of "Range Table" in the
parent object rather
than inside the array.
Attached a patch to address this which also includes a test.
Repro:
LOAD 'pg_overexplain';
CREATE TABLE t1 (id serial PRIMARY KEY, val text);
CREATE TABLE t2 (id serial PRIMARY KEY, a_id int REFERENCES t1(id), data
text);
INSERT INTO t1 VALUES (1, 'x'), (2, 'y');
INSERT INTO t2 VALUES (1, 1, 'd1'), (2, 2, 'd2');
EXPLAIN (FORMAT JSON, RANGE_TABLE)
EXPLAIN (FORMAT JSON, RANGE_TABLE)
SELECT * FROM t1 a JOIN t2 b ON a.id = b.a_id WHERE a.id = 1; "
| tail -n +2 | python3 -c "import json,sys; json.loads(sys.stdin.read());
print('VALID JSON')"
Thanks,
Satya
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix pg_overexplain to emit valid output with RANGE_TABLE option.
- 6723d462db5a 18.4 landed
- 059cf7f58d23 19 (unreleased) landed