Re: pg_stat_statements oddity with track = all

Поиск
Список
Период
Сортировка
От Sergei Kornilov
Тема Re: pg_stat_statements oddity with track = all
Дата
Msg-id 1110111606984390@mail.yandex.ru
обсуждение исходный текст
Ответ на Re: pg_stat_statements oddity with track = all  (legrand legrand <legrand_legrand@hotmail.com>)
Ответы Re: pg_stat_statements oddity with track = all  (Julien Rouhaud <rjuju123@gmail.com>)
Список pgsql-hackers
Hello

> To get an increase in the number of records that means that the same
> statement
> would appear at top level AND nested level. This seems a corner case with
> very low
> (neglectible) occurence rate.

+1
I think splitting fields into plans_toplevel / plans_nested will be less convenient. And more code with higher chance
ofcopypaste errors
 

regards, Sergei



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

Предыдущее
От: Kyotaro Horiguchi
Дата:
Сообщение: Re: Huge memory consumption on partitioned table with FKs
Следующее
От: Julien Rouhaud
Дата:
Сообщение: Re: pg_stat_statements oddity with track = all