adrian.klaver@aklaver.com writes:
> test=> set timezone = DEFAULT;
> SET
> test=> set timezone = LOCAL;
> ERROR: invalid value for parameter "TimeZone": "local"
> test=> set time zone LOCAL;
> SET
"SET TIME ZONE LOCAL" is a SQL-standard-mandated variant way of writing
"set timezone to default", following the SQL committee's time-honored
principle of never using orthogonal syntax if somebody can think of an
idiosyncratic way instead.
Given the way that our grammar is set up, the only way we could handle
"set timezone = LOCAL" would be to allow LOCAL as a synonym for DEFAULT
for *all* SET variables. That doesn't seem like a particularly good
idea.
> The docs:
> https://www.postgresql.org/docs/9.5/static/sql-set.html
> say the last two commands should yield the same result.
AFAICS, the docs show the syntax restriction accurately:
SET [ SESSION | LOCAL ] configuration_parameter { TO | = } { value | 'value' | DEFAULT }
SET [ SESSION | LOCAL ] TIME ZONE { timezone | LOCAL | DEFAULT }
LOCAL is not listed as a valid alternative for the first syntax.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
