Re: pg_stat_activity query_id

Поиск
Список
Период
Сортировка
От Erik Wienhold
Тема Re: pg_stat_activity query_id
Дата
Msg-id 1279536236.296763.1683901055904@office.mailbox.org
обсуждение исходный текст
Ответ на Re: pg_stat_activity query_id  (kaido vaikla <kaido.vaikla@gmail.com>)
Ответы Re: pg_stat_activity query_id  (kaido vaikla <kaido.vaikla@gmail.com>)
Список pgsql-admin
> On 12/05/2023 15:34 CEST kaido vaikla <kaido.vaikla@gmail.com> wrote:
>
> I changed my query. "xact_start is not NULL" must show only active queries.
> I see my own query with query_id, pwatch2 (https://github.com/cybertec-postgresql/pgwatch2)
> queries with query_id, but application queries (PostgreSQL JDBC Driver) are
> without query_id. Any idea why?

As I wrote in my previous message, pg_catalog.pg_db_role_setting will tell you
if compute_query_id is set for any user/database combination which overrides
the system-wide default from postgresql.conf for new sessions.

Your query results don't include usernames and databases.  I assume the JDBC
connections are with a different user or on a different database than the psql
and pgwatch2 connections for which query_id is calculated.

Could be that postgresql.conf sets compute_query_id=off and only the users that
you used for psql and pgwatch2 have compute_query_id={on,auto}.

Then there's also the chance that the applications using the JDBC driver set
compute_query_id=off before sending queries.  Doesn't explain however why this
would also be the case for that one connection from IntelliJ IDEA (which I
assume uses JDBC as well).  I doubt that JDBC sets compute_query_id=off by
default.

My guess is user-specific session defaults.

--
Erik



В списке pgsql-admin по дате отправления:

Предыдущее
От: kaido vaikla
Дата:
Сообщение: Re: pg_stat_activity query_id
Следующее
От: Alex Balashov
Дата:
Сообщение: Unexplained rapid growth in memory usage of idle backends