Re: SET ROLE documentation improvement
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>,
"Andrey M. Borodin" <x4mmm@yandex-team.ru>, Yurii Rashkovskii <yrashk@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2024-04-11T15:36:52Z
Lists: pgsql-hackers
On Thu, Apr 11, 2024 at 10:03 AM Nathan Bossart <nathandbossart@gmail.com> wrote: > On Thu, Apr 11, 2024 at 10:33:15AM +0900, Michael Paquier wrote: > > On Tue, Apr 09, 2024 at 09:21:39AM +0300, Andrey M. Borodin wrote: > >> Can I ask you please to help me with determining status of CF item > >> [0]. Is it committed or there's something to move to next CF? > > > > Only half of the patch has been applied as of 3330a8d1b792. Yurii and > > Nathan, could you follow up with the rest? Moving the patch to the > > next CF makes sense, and the last thread update is rather recent. > > AFAICT there are two things remaining: > > * Remove the "they lose their superuser privileges" note. > * Note that SET ROLE and SET SESSION AUTHORIZATION are exceptions. > > While I think these are good changes, I don't sense any urgency here, so > I'm treating this as v18 material at this point. I suggest that we close the existing CF entry as committed and somebody can start a new one for whatever remains. I think that will be less confusing. -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
doc: Note exceptions for SET ROLE's effect on privilege checks.
- 953cf49e166a 17.0 landed
-
doc: Clarify requirements for SET ROLE.
- d82dc79ba03c 16.3 landed
- 3330a8d1b792 17.0 landed