On Thu, Nov 5, 2020 at 3:49 PM Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > We could also make it a protocol message, but it would essentially > implement the same thing, just again separately. And then you'd have no > support to inspect the current setting, test out different settings > interactively, etc. That seems pretty wasteful and complicated for no > real gain.
But ... if it's just a GUC, it can be set by code on the server side that the client knows nothing about, breaking the client. That seems pretty bad to me. -- Robert Haas EDB: http://www.enterprisedb.com
