From: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Using stat collector for collecting long SQL |
Date: | 2020-02-27 13:12:58 |
Message-ID: | 1582809178796-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
> There is a often problem with taking source of long SQL strings. The
> pg_stat_activity field query is reduced to some short limit and is not too
> practical to increase this limit.
I thought it was "old story", since that track_activity_query_size can be
increased widely:
https://www.postgresql.org/message-id/flat/7b5ecc5a9991045e2f13c84e3047541d%40postgrespro.ru
[...]
> It can be base for implementation EXPLAIN PID ?
+1 for this concept, that would be very usefull for diagnosing stuck
queries.
Until now the only proposal I saw regarding this was detailled in
https://www.postgresql.org/message-id/1582756552256-0.post@n3.nabble.com
a prerequisite to be able to use extension postgrespro/pg_query_state
Regards
PAscal
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-02-27 13:37:24 | Re: Improve handling of parameter differences in physical replication |
Previous Message | Michael Paquier | 2020-02-27 12:55:31 | Re: [Proposal] Level4 Warnings show many shadow vars |