Re: pgsql: Fix search_path to a safe value during maintenance operations. - Mailing list pgsql-committers

From Jeff Davis
Subject Re: pgsql: Fix search_path to a safe value during maintenance operations.
Date
Msg-id 4df537f5a0d8c0ceac3eec3809d1144880b8e76d.camel@j-davis.com
Whole thread Raw
In response to Re: pgsql: Fix search_path to a safe value during maintenance operations.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Fix search_path to a safe value during maintenance operations.
List pgsql-committers
On Tue, 2023-06-13 at 16:23 -0400, Tom Lane wrote:
> What I'm concerned about is making such a fundamental semantics
> change
> post-beta1.

I have added the patch to the July CF for v17.

If someone does feel like something should be done for v16, David G.
Johnston posted one possibility here:

https://www.postgresql.org/message-id/CAKFQuwaVJkM9u+qpOaom2UkPE1sz0BASF-E5amxWPxncUhm4Hw@mail.gmail.com

But as Noah pointed out, there are other privileges that can be abused,
so a workaround for 16 might not be important if we have a likely fix
for MAINTAIN coming in 17.

Regards,
    Jeff Davis




pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: intarray: Prevent out-of-bound memory reads with gist__int_ops
Next
From: Masahiko Sawada
Date:
Subject: pgsql: Replace GUC_UNIT_MEMORY|GUC_UNIT_TIME with GUC_UNIT.