Re: is_superuser versus set_config_option's parallelism check
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, Robert Haas <robertmhaas@gmail.com>
Date: 2024-08-09T20:30:21Z
Lists: pgsql-hackers
On Fri, Aug 09, 2024 at 04:04:15PM -0400, Tom Lane wrote: > Nathan Bossart <nathandbossart@gmail.com> writes: >> From a couple of quick tests, it looks like setting >> "current_role_is_superuser" directly works. > > Yeah, I had been thinking along the same lines. Here's a draft > patch. (Still needs some attention to nearby comments, and I can't > avoid the impression that the miscinit.c code in this area could > use refactoring.) Hm. That's a bit more code than I expected. > A problem with this is that it couldn't readily be back-patched > further than v14, since we didn't have ReportChangedGUCOptions > before that. Maybe that doesn't matter; given the lack of > previous complaints, maybe we only need to fix this in HEAD. Another option might be to introduce a new GUC flag or source for anything we want to bypass the check (perhaps with the stipulation that it must also be marked PGC_INTERNAL). I think a new flag would require moving the parallel check down a stanza, but that seems fine. A new source would allow us to limit the damage to specific SetConfigOption() call-sites, but I haven't thought through that idea fully. -- nathan
Commits
-
Allow adjusting session_authorization and role in parallel workers.
- 364de74cff28 18.0 landed
- f3ab5d3a2d19 16.5 landed
- adf9808fa966 13.17 landed
- adc28d01e98b 12.21 landed
- 546a26b3d8df 14.14 landed
- 2f4e895be760 15.9 landed
- 2b8d33f66c13 17.0 landed
-
Fix failure to verify PGC_[SU_]BACKEND GUCs in pg_file_settings view.
- 059de3ca4766 17.0 cited