From: Jacque <jacqueedmund@gmail.com>
To: pgsql-admin@postgresql.org
Subject: creative work-arounds to obtain auto_explain's benefits for non-superuser
Date: Thu, 13 Feb 2020 16:46:16 -0500
Message-ID: <42f470b5-8ee7-d3f8-320a-820c12329e63@gmail.com> (raw)
I gotta admit. The logging of auto_explain is an embarrassment of riches.
But most operational work is not done under the superuser role but one
with the lowest opportunity risk of compromise. I'd like to be
embarrassed by an operator role. Any Mcgeyors out there with ideas to
be thus embarrased?
Honestly, the only solution I've come up with is to duplicate every
non-superuser SQL object in a superuser-ONLY schema and have the super
user perform the same SQL as the operator role (perhaps on alternate
days). Then I could configure that superuser work with all the
auto_explain.* settings I could ever want. As I write this, its clear
to me that an extension called "Rogue" is the perfect name that could
excise the essential abilities of an extension without obtaining full
superuser powers, eh... ur privaledges. God bless my C if he deems to
grant me that mission.
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
Subject: Re: creative work-arounds to obtain auto_explain's benefits for non-superuser
In-Reply-To: <42f470b5-8ee7-d3f8-320a-820c12329e63@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