To: pgsql-admin@postgresql.org
From: Jacque <jacqueedmund@gmail.com>
Subject: creative work-arounds to obtain auto_explain's benefits for
 non-superuser
Message-ID: <42f470b5-8ee7-d3f8-320a-820c12329e63@gmail.com>
Date: Thu, 13 Feb 2020 16:46:16 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

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.