Re: pgsql: Fix search_path to a safe value during maintenance operations.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations.
Date: 2023-06-15 04:59:40
Message-ID: 4df537f5a0d8c0ceac3eec3809d1144880b8e76d.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2023-06-15 08:06:17 pgsql: Replace GUC_UNIT_MEMORY|GUC_UNIT_TIME with GUC_UNIT.
Previous Message Michael Paquier 2023-06-15 04:46:18 pgsql: intarray: Prevent out-of-bound memory reads with gist__int_ops

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2023-06-15 05:07:13 Re: Order changes in PG16 since ICU introduction
Previous Message Jeff Davis 2023-06-15 04:47:52 [17] CREATE COLLATION default provider