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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations.
Date: 2023-06-30 05:09:21
Message-ID: 20230630050921.GA2640352@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Jun 29, 2023 at 08:53:56PM -0400, Tom Lane wrote:
> I'm leaning to Robert's thought that we need to revert this for now,
> and think harder about how to make it work cleanly and safely.

Since it sounds like this is headed towards a revert, here's a patch for
removing MAINTAIN and pg_maintain.

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
v1-0001-Revert-MAINTAIN-privilege-and-pg_maintain-predefi.patch text/x-diff 69.7 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2023-06-30 06:48:02 pgsql: Introduce long options in pg_archivecleanup
Previous Message Michael Paquier 2023-06-30 04:55:48 pgsql: Fix marking of indisvalid for partitioned indexes at creation

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-06-30 05:13:32 Re: vacuumdb/clusterdb/reindexdb: allow specifying objects to process in all databases
Previous Message jian he 2023-06-30 04:50:25 Re: Do we want a hashset type?