You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Disallow setting bogus GUCs within an extension's reserved namespace.
Commit75d2206 tried to throw a warning for setting a custom GUC whoseprefix belongs to a previously-loaded extension, if there is no such GUCdefined by the extension. But that caused unstable behavior withparallel workers, because workers don't necessarily load extensions andGUCs in the same order their leader did. To make that work safely, wehave to completely disallow the case. We now actually remove any suchGUCs at the time of initial extension load, and then throw an error notjust a warning if you try to add one later. While this might create acompatibility issue for a few people, the improvement in error-detectioncapability seems worth it; it's hard to believe that there's any gooduse-case for choosing such GUC names.This also un-reverts5609cc0 (Rename EmitWarningsOnPlaceholders() toMarkGUCPrefixReserved()), since that function's old name is now evenmore of a misnomer.Florin Irion and Tom LaneDiscussion:https://postgr.es/m/1902182.1640711215@sss.pgh.pa.us