Re: nested queries vs. pg_stat_activity

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: nested queries vs. pg_stat_activity
Дата
Msg-id CA+TgmoaM0ME6ESu5rFgkz0g9Z-BLox5_+d8s328Xgn3r_LaGGQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: nested queries vs. pg_stat_activity  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: nested queries vs. pg_stat_activity  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
On Mon, Aug 10, 2020 at 4:09 PM Magnus Hagander <magnus@hagander.net> wrote:
> Would it even solve the problem for them? pg_stat_statements collects aggregate stats and not a view of what's
happeningright now -- so it'd be mixing two different types of values. And it would get worse if the same thing is
executedmultiple times concurrently. 

True. You could find that you have a queryId that had already been
evicted from the table.

I think it's better to look for a more direct solution to this problem.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Allow some recovery parameters to be changed with reload
Следующее
От: Jim Nasby
Дата:
Сообщение: Re: autovac issue with large number of tables