Re: Using stat collector for collecting long SQL
| От | legrand legrand |
|---|---|
| Тема | Re: Using stat collector for collecting long SQL |
| Дата | |
| Msg-id | 1582809178796-0.post@n3.nabble.com обсуждение исходный текст |
| Ответ на | Using stat collector for collecting long SQL (Pavel Stehule <pavel.stehule@gmail.com>) |
| Список | 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
В списке pgsql-hackers по дате отправления: