From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
---|---|
To: | veem v <veema0000(at)gmail(dot)com> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: When manual analyze is needed |
Date: | 2024-03-05 18:22:48 |
Message-ID: | CAKAnmm+T9+x_ev-21eEHYUfJiWu9LJyjePWifxkvqNH2uCo+BA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Lok P | 2024-03-05 19:05:02 | Re: Is partition pruning impacted by data type |
Previous Message | grimy.outshine830 | 2024-03-05 18:21:33 | Re: pgBadger: Cannot find any log entries from systemd-journald |