Re: When manual analyze is needed - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: When manual analyze is needed
Date
Msg-id CAKAnmm+T9+x_ev-21eEHYUfJiWu9LJyjePWifxkvqNH2uCo+BA@mail.gmail.com
Whole thread Raw
In response to Re: When manual analyze is needed  (veem v <veema0000@gmail.com>)
List pgsql-general
We were planning to have the auto_explain extension added and set the log_min_duration to ~5 seconds and log_analyze to true. So that all the queries going above that time period will be logged and provide detailed information on the exact point of bottleneck. Will it be a good idea to set it on production DB which is a highly active database? or should we only have the extension added but only set the parameters while we debug some performance issue and then reset it back after we are done.

I would not use log_analyze on a highly active production db. Even on a dev system, use it carefully as it has some downsides. The log_min_duration of 5s should be fine everywhere, however.

Cheers,
Greg 

pgsql-general by date:

Previous
From: grimy.outshine830@aceecat.org
Date:
Subject: Re: pgBadger: Cannot find any log entries from systemd-journald
Next
From: Lok P
Date:
Subject: Re: Is partition pruning impacted by data type