Re: New GUC to sample log queries
От | Tomas Vondra |
---|---|
Тема | Re: New GUC to sample log queries |
Дата | |
Msg-id | 46944a05-55b3-c5c8-918a-89d65893856e@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: New GUC to sample log queries (Adrien Nayrat <adrien.nayrat@anayrat.info>) |
Ответы |
Re: New GUC to sample log queries
|
Список | pgsql-hackers |
On 11/18/18 10:52 AM, Adrien Nayrat wrote: > ... > Alors, I wonder if we should use the same logic for other parameters, such as > log_statement_stats > log_parser_stats > log_planner_stats > log_executor_stats > > It was mentioned in this thread > https://www.postgresql.org/message-id/20180710183828.GB3890%40telsasoft.com You mean apply sampling to those logging options too? I doubt that would be very useful, as the those options are IMHO meant for development. Maybe tracking some of the info would be useful, but integrating it into pg_stat_statements seems like a better solution than just dumping it into the server log. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: