On Thu, Feb 1, 2024 at 7:33 AM Bruce Momjian <br...@momjian.us> wrote: > On Tue, Jan 30, 2024 at 04:25:12PM -0500, Robert Haas wrote: > > I don't think we should pretend like one of the two paragraphs above > > is valid and the other is hot garbage. That's not solving anything. We > > can't resolve the tension between those two things in either direction > > by somebody hammering on the side of the argument that they believe to > > be correct and ignoring the other one. > > What if we generate log messages when certain commands are used, like > ALTER TABLE? We could have GUC which controls which commands are > logged.
Well, as I understand it, that doesn't solve the problem here. The problem some people want to solve here seems to be: On my system, the PostgreSQL configuration parameters are being managed by $EXTERNAL_TOOL. Therefore, they should not be managed by PostgreSQL itself. Therefore, if someone uses ALTER SYSTEM, they've made a mistake, so we should give them an ERROR telling them that, like: ERROR: you're supposed to update the configuration via k8s, not ALTER SYSTEM, you dummy! DETAIL: Stop being an idiot. The exact message text might need some wordsmithing. :-) -- Robert Haas EDB: http://www.enterprisedb.com
