| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Set query_id for query contained in utility statement |
| Date: | 2024-10-22 05:09:03 |
| Message-ID: | Zxczb8b8srjARwkE@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v10-0001-Track-location-to-extract-relevant-part-in-neste.patch | text/x-diff | 45.5 KB |
| v10-0002-Set-query_id-for-queries-contained-in-utility-st.patch | text/x-diff | 22.8 KB |
| v10-0003-Use-view-s-definition-as-query-string-on-a-mater.patch | text/x-diff | 6.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-10-22 05:29:34 | Row pattern recognition |
| Previous Message | Michael Paquier | 2024-10-22 05:06:16 | Re: Set query_id for query contained in utility statement |