Nathan Bossart 9eb6068fb6 Allow resetting unknown custom GUCs with reserved prefixes. ... Currently, ALTER DATABASE/ROLE/SYSTEM RESET [ALL] with an unknown custom GUC with a prefix reserved by MarkGUCPrefixReserved() errors (unless a superuser runs a RESET ALL variant). This is problematic for cases such as an extension library upgrade that removes a GUC. To fix, simply make sure the relevant code paths explicitly allow it. Note that we require superuser or privileges on the parameter to reset it. This is perhaps a bit more restrictive than is necessary, but it's not clear whether further relaxing the requirements is safe. Oversight in commit 88103567cb. The ALTER SYSTEM fix is dependent on commit 2d870b4aef, which first appeared in v17. Unfortunately, back-patching that commit would introduce ABI breakage, and while that breakage seems unlikely to bother anyone, it doesn't seem worth the risk. Hence, the ALTER SYSTEM part of this commit is omitted on v15 and v16. Reported-by: Mert Alev <mert@futo.org> Reviewed-by: Laurenz Albe <laurenz.albe@cybertec.at> Discussion: https://postgr.es/m/18964-ba09dea8c98fccd6%40postgresql.org Backpatch-through: 15		2025-08-01 16:52:11 -05:00
..
expected	Allow resetting unknown custom GUCs with reserved prefixes.	2025-08-01 16:52:11 -05:00
sql	Allow resetting unknown custom GUCs with reserved prefixes.	2025-08-01 16:52:11 -05:00
t	Introduce PG_MODULE_MAGIC_EXT macro.	2025-03-26 11:06:12 -04:00
.gitignore	Add a simple test for contrib/auto_explain.	2021-01-24 14:59:33 -05:00
auto_explain.c	Revert "Don't lock partitions pruned by initial pruning"	2025-05-22 17:02:35 +09:00
Makefile	Allow resetting unknown custom GUCs with reserved prefixes.	2025-08-01 16:52:11 -05:00
meson.build	Allow resetting unknown custom GUCs with reserved prefixes.	2025-08-01 16:52:11 -05:00