From: Jacque <jacqueedmund@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: "NEVER" cautioned to auto_explain's log_analyze parameter on Production
Date: Wed, 26 Feb 2020 16:17:21 -0500
Message-ID: <fb1497da-6025-19d9-0bf1-ba95c5c08bfa@gmail.com> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jacqueedmund@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: "NEVER" cautioned to auto_explain's log_analyze parameter on Production
In-Reply-To: <fb1497da-6025-19d9-0bf1-ba95c5c08bfa@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox