On Thu, Apr 7, 2016 at 10:45 AM, Stephen Frost wrote:
> Use GRANT system to manage access to sensitive functions
>
> Now that pg_dump will properly dump out any ACL changes made to
> functions which exist in pg_catalog, switch to using the GRANT system
> to manage access to those functions.
>
> Th
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Stephen Frost writes:
> > Use GRANT system to manage access to sensitive functions
>
> This patch series seems approximately three catversion bumps
> shy of a load ...
Blargh. I told myself at three different times tonight to remember to
bump catversion.
Stephen Frost writes:
> Use GRANT system to manage access to sensitive functions
This patch series seems approximately three catversion bumps
shy of a load ...
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes
On Thu, Apr 7, 2016 at 10:45 AM, Stephen Frost wrote:
> Use GRANT system to manage access to sensitive functions
>
> Now that pg_dump will properly dump out any ACL changes made to
> functions which exist in pg_catalog, switch to using the GRANT system
> to manage access to those functions.
>
> Th
Use GRANT system to manage access to sensitive functions
Now that pg_dump will properly dump out any ACL changes made to
functions which exist in pg_catalog, switch to using the GRANT system
to manage access to those functions.
This means removing 'if (!superuser()) ereport()' checks from the
fun
