Re: Possibility to disable `ALTER SYSTEM`
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
Bruce Momjian <bruce@momjian.us>,
Maciek Sakrejda <m.sakrejda@gmail.com>,
Tom Lane <tgl@sss.pgh.pa.us>,
Joel Jacobson <joel@compiler.org>,
Andrew Dunstan <andrew@dunslane.net>,
Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Magnus Hagander <magnus.hagander@redpill-linpro.com>
Date: 2024-03-18T13:09:04Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add allow_alter_system GUC.
- d3ae2a24f265 17.0 landed
-
Rename COMPAT_OPTIONS_CLIENT to COMPAT_OPTIONS_OTHER.
- de7e96bd0fc6 17.0 landed
-
Remove support for version-0 calling conventions.
- 5ded4bd21403 10.0 cited
> On 18 Mar 2024, at 13:57, Robert Haas <robertmhaas@gmail.com> wrote: > my proposal is something like this, taking a > bunch of text from Jelte's patch and some inspiration from Magnus's > earlier remarks: I still think any wording should clearly mention that settings in the file are still applied. The proposed wording says to implicitly but to avoid confusion I think it should be explicit. > Perhaps figuring out how to > document this is best left to a separate thread, and there's also the > question of whether a new section that talks about this also ought to > talk about anything else. But I feel like we're way overdue to do > something about this. Seconded, both that it needs to be addressed and that it should be done on a separate thread from this one. -- Daniel Gustafsson