postgres

History

Tom Lane 88103567cb Disallow setting bogus GUCs within an extension's reserved namespace. Commit `75d22069e` tried to throw a warning for setting a custom GUC whose prefix belongs to a previously-loaded extension, if there is no such GUC defined by the extension. But that caused unstable behavior with parallel workers, because workers don't necessarily load extensions and GUCs in the same order their leader did. To make that work safely, we have to completely disallow the case. We now actually remove any such GUCs at the time of initial extension load, and then throw an error not just a warning if you try to add one later. While this might create a compatibility issue for a few people, the improvement in error-detection capability seems worth it; it's hard to believe that there's any good use-case for choosing such GUC names. This also un-reverts `5609cc01c` (Rename EmitWarningsOnPlaceholders() to MarkGUCPrefixReserved()), since that function's old name is now even more of a misnomer. Florin Irion and Tom Lane Discussion: https://postgr.es/m/1902182.1640711215@sss.pgh.pa.us		4 years ago
..
expected	Include permissive/enforcing state in sepgsql log messages.	4 years ago
sql	…
.gitignore	…
Makefile	…
database.c	Update copyright for 2022	4 years ago
dml.c	Update copyright for 2022	4 years ago
hooks.c	Disallow setting bogus GUCs within an extension's reserved namespace.	4 years ago
label.c	Update copyright for 2022	4 years ago
launcher	Update copyright for 2022	4 years ago
proc.c	Update copyright for 2022	4 years ago
relation.c	Update copyright for 2022	4 years ago
schema.c	Update copyright for 2022	4 years ago
selinux.c	Include permissive/enforcing state in sepgsql log messages.	4 years ago
sepgsql-regtest.te	…
sepgsql.h	Include permissive/enforcing state in sepgsql log messages.	4 years ago
sepgsql.sql.in	…
test_sepgsql	…
uavc.c	Include permissive/enforcing state in sepgsql log messages.	4 years ago