"NEVER" cautioned to auto_explain's log_analyze parameter on Production
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: pgsql-admin@xxxxxxxxxxxxxxxxxxxx
- Subject: "NEVER" cautioned to auto_explain's log_analyze parameter on Production
- From: Jacque <jacqueedmund@xxxxxxxxx>
- Date: Wed, 26 Feb 2020 16:17:21 -0500
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
I've seen it said to "NEVER" apply auto_explain's log_analyze parameter
on Production. I get the general foreboding doom that can be beset by
a highly looping control structure eating up disk space (with no
indication of its exit condition time) but is genrous-disk-writes
pretty much the only reason for avoiding this in folk's opinion? And
say a well-mannered connection using it could be safe in production?
Seems to be afterall what the pganalyze folks must be doing with their
commercial product afterall.
[Index of Archives]
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Virtualization Tools]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Linux Audio Users]
[Yosemite Questions]
[Linux Kernel]
[Linux SCSI]
[XFree86]