Re: Set query_id for query contained in utility statement

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es

From: Michael Paquier <michael@paquier.xyz>

To: Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>

Cc: jian he <jian.universality@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2024-10-22T05:09:03Z

Lists: pgsql-hackers

Attachments

v10-0001-Track-location-to-extract-relevant-part-in-neste.patch (text/x-diff) patch v10-0001
v10-0002-Set-query_id-for-queries-contained-in-utility-st.patch (text/x-diff) patch v10-0002
v10-0003-Use-view-s-definition-as-query-string-on-a-mater.patch (text/x-diff) patch v10-0003

On Tue, Oct 22, 2024 at 02:06:16PM +0900, Michael Paquier wrote:
> I've looked at 0001, and finished by splitting the case of all-level
> tracking with the multi-statements as the resulting table was feeling
> heavily bloated, particularly because of MERGE that spawned in
> multiple lines even if there were less entries.  The rest, except for
> some styling inconsistencies, was feeling OK.

And of course I have forgotten to attach a rebase of the remaining
patches..
--
Michael

Commits

Set query ID for inner queries of CREATE TABLE AS and DECLARE
- 6b652e6ce85a 18.0 landed
Track more precisely query locations for nested statements
- 499edb09741b 18.0 landed
pg_stat_statements: Add tests for nested queries with level tracking
- 45e0ba30fc40 18.0 landed
Fix race condition in COMMIT PREPARED causing orphaned 2PC files
- cf4401fe6cf5 18.0 cited