| From: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com> |
| Cc: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com> |
| Subject: | Re: POC: Extension for adding distributed tracing - pg_tracing |
| Date: | 2023-12-15 19:05:38 |
| Message-ID: | CAN-LCVOW7XtT3CYO7AfAXhD8egp7=aHVF2NxS3BK=9YjGGqarQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
Overall solution looks good for me except SQL Commenter - query
instrumentation
with SQL comments is often not possible on production systems. Instead
the very often requested feature is to enable tracing for a given single
query ID,
or several (very limited number of) queries by IDs. It could be done by
adding
SQL function to add and remove query ID into a list (even array would do)
stored in top tracing context.
Great job, thank you!
--
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2023-12-15 19:07:29 | Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements |
| Previous Message | Tom Lane | 2023-12-15 19:01:07 | Re: LargeObjectRelationId vs LargeObjectMetadataRelationId, redux |