Re: MAINTAIN privilege -- what do we need to un-revert it? - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: MAINTAIN privilege -- what do we need to un-revert it?
Date
Msg-id bfbcf235ee774ab4b6225dfba7be25a60ac01808.camel@j-davis.com
Whole thread Raw
In response to Re: MAINTAIN privilege -- what do we need to un-revert it?  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: MAINTAIN privilege -- what do we need to un-revert it?
List 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




pgsql-hackers by date:

Previous
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Changing the default random_page_cost value
Next
From: Tom Lane
Date:
Subject: Re: Better error reporting from extension scripts (Was: Extend ALTER OPERATOR)