Re: MAINTAIN privilege -- what do we need to un-revert it?
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Nathan Bossart <nathandbossart@gmail.com>, Yugo NAGATA
<nagata@sraoss.co.jp>
Cc: Noah Misch <noah@leadboat.com>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers@postgresql.org, Joe Conway <mail@joeconway.com>, Robert Haas <robertmhaas@gmail.com>
Date: 2024-09-27T16:22:48Z
Lists: pgsql-hackers
On Fri, 2024-09-27 at 10:34 -0500, Nathan Bossart wrote: > On Fri, Sep 27, 2024 at 12:42:34PM +0900, Yugo NAGATA wrote: > > I agree with you. I overlooked WITH NO DATA. > > I attached a updated patch. > > Thanks. Unless someone objects, I plan to commit this shortly. The command is run effectively in two parts: the CREATE part and the REFRESH part. The former just uses the session search path, while the latter uses the safe search path. I suggest that we add the wording to the <replaceable>query</replaceable> portion of the doc, near "security- restricted operation". Regards, Jeff Davis
Commits
-
doc: Note that CREATE MATERIALIZED VIEW restricts search_path.
- d8ebcac547d7 18.0 landed
- 18cea252ac74 17.1 landed
-
Small refactoring around ExecCreateTableAs().
- 7926a9a80f6d 18.0 landed
-
Add is_create parameter to RefreshMatviewByOid().
- ca2eea3ac89a 18.0 landed
-
Remove unused ParamListInfo argument from ExecRefreshMatView.
- f683d3a4ca6d 18.0 landed
-
When creating materialized views, use REFRESH to load data.
- 4b74ebf726d4 18.0 landed
- b4da732fd64e 17.0 landed
-
Add missing RestrictSearchPath() calls.
- a15b0edb5dd9 17.0 landed
- 8e28778ce396 18.0 landed
-
Fix search_path to a safe value during maintenance operations.
- 2af07e2f749a 17.0 landed
-
Revert MAINTAIN privilege and pg_maintain predefined role.
- 151c22deee66 17.0 cited
-
Avoid repeated name lookups during table and index DDL.
- 5f173040e324 9.4.0 cited
-
Add a materialized view relations.
- 3bf3ab8c5636 9.3.0 cited