Re: [HACKERS] search path security issue? - Mailing list pgsql-hackers

From Joe Conway
Subject Re: [HACKERS] search path security issue?
Date
Msg-id f3ee3b67-82ee-9a67-23be-c6ba199a80fd@joeconway.com
Whole thread Raw
In response to Re: [HACKERS] search path security issue?  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] search path security issue?
List pgsql-hackers
On 10/06/2017 12:52 AM, Magnus Hagander wrote:
> It would be a nice feature to have in general, like a "basic guc
> permissions" thing. At least allowing a superuser to prevent exactly
> this. You could argue the same thing for example for memory parameters
> and such. We have no permissions at all when it comes to userset gucs
> today -- and of course, if something should be added about this, it
> should be done in a way that works for all the userset variables, not
> just search_path. 

+1

I have wished for exactly that more than once before.

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Discussion on missing optimizations