Bruce Momjian <[EMAIL PROTECTED]> writes:
> How about sending an INFO or special taged message to the client when
> there is a GUC change, and have report_changes as a GUC variable that
> controls it?
Having such a variable would break the client libraries that need the
information. They won't stop needing the info just because some DBA
thinks it's a good idea to save a few bytes of bandwidth ...
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
