Stephen Frost <sfr...@snowman.net> writes: > In reviewing this patch, I also noticed that it's set up to assume a > 'true' result when a variable can't be parsed by ParseVariableBool.
I suppose that's meant to be backwards-compatible with the current behavior: regression=# \timing foo unrecognized value "foo" for "\timing"; assuming "on" Timing is on. but I agree that if we're changing things in this area, that would be high on my list of things to change. I think what we want going forward is to disallow setting "special" variables to invalid values, and that should hold both for regular variables that have special behaviors, and for the special-syntax cases like \timing. regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers