From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
---|---|
To: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dave Cramer <davecramer(at)postgres(dot)rocks> |
Subject: | Re: protocol support for labels |
Date: | 2025-03-11 10:03:34 |
Message-ID: | CALdSSPiA4nDBmPg5s38YnfWMX79hyhjEB=Hgyf7cmE8fQRDoSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 11 Mar 2025 at 11:09, Jeremy Schneider <schneider(at)ardentperf(dot)com> wrote:
> observability frameworks like OpenTelemetry support tracing through all
> layers of a stack, and trace_ids can even be passed into sql with
> extensions like sqlcommenter. however sqlcommenter puts the trace_id
> into a comment which effectively breaks all the utility of
> pg_stat_statements since each query has a unique trace_id.
>
There are some other use-cases:
1) RO-RW routing. Users can pass target-session-attrs to the server
within query labels to hint about its need. Useful when some kind of
proxy (odyssey,pgbouncer,spqr,pgpool II, pgcat, pg_doorman) is used.
2) pg_comment_stats uses comments in the query to accumulate statistics. [0]
However, I don't think PostgreSQL community is open for this big
change for much (non-big) matters.
[0] git(at)github(dot)com:munakoiso/pg_comment_stats.git
--
Best regards,
Kirill Reshke
From | Date | Subject | |
---|---|---|---|
Next Message | Rushabh Lathia | 2025-03-11 10:15:46 | Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints |
Previous Message | Ilia Evdokimov | 2025-03-11 09:58:06 | Re: explain analyze rows=%.0f |