pgsql: Fix pg_overexplain to emit valid output with RANGE_TABLE option.
| От | Amit Langote |
|---|---|
| Тема | pgsql: Fix pg_overexplain to emit valid output with RANGE_TABLE option. |
| Дата | |
| Msg-id | E1wDF5g-001CRS-2p@gemulon.postgresql.org обсуждение |
| Список | pgsql-committers |
Fix pg_overexplain to emit valid output with RANGE_TABLE option. overexplain_range_table() emitted the "Unprunable RTIs" and "Result RTIs" properties before closing the "Range Table" group. In the JSON and YAML formats the Range Table group is rendered as an array of RTE objects, so emitting key/value pairs inside it produced structurally invalid output. The XML format had a related oddity, with these elements nested inside <Range-Table> rather than appearing as its siblings. These fields are properties of the PlannedStmt as a whole, not of any individual RTE, so close the Range Table group before emitting them. They now appear as siblings of "Range Table" in the parent Query object, which is what was intended. Also add a test exercising FORMAT JSON with RANGE_TABLE so that any future regression in the output structure is caught. Reported-by: Satyanarayana Narlapuram <satyanarlapuram@gmail.com> Author: Satyanarayana Narlapuram <satyanarlapuram@gmail.com> Reviewed-by: Amit Langote <amitlangote09@gmail.com> Reviewed-by: Chao Li <li.evan.chao@gmail.com> Discussion: https://postgr.es/m/CAHg+QDdDrdqMr98a_OBYDYmK3RaT7XwCEShZfvDYKZpZTfOEjQ@mail.gmail.com Backpatch-through: 18 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/059cf7f58d23fc53423e4e58feaaa717faef53c5 Modified Files -------------- contrib/pg_overexplain/expected/pg_overexplain.out | 122 ++++++++++++++++++++- contrib/pg_overexplain/pg_overexplain.c | 12 +- contrib/pg_overexplain/sql/pg_overexplain.sql | 6 + 3 files changed, 134 insertions(+), 6 deletions(-)
В списке pgsql-committers по дате отправления: