From: | Shay Rojansky <roji(at)roji(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | "localtime" value in TimeZone |
Date: | 2019-07-24 15:19:40 |
Message-ID: | CADT4RqCCnj6FKLisvT8tTPfTP4azPhhDFJqDF1JfBbOH5w4oyQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings everyone.
In (certain) out-of-the-box PostgreSQL installations, the timezone GUC is
set to "localtime", which seems to mean to query the OS for the value.
Unless I'm mistaken, the issue with this is that it doesn't allow clients
inspecting the TimeZone GUC to actually know what timezone the server is
in, making the GUC largely useless (and creates friction as the GUC can't
be expected to always contain valid IANA/Olson values). It would be more
useful if PostgreSQL exposed the actual timezone provided by the OS.
Does this make sense?
As a side note, there doesn't seem to be any specific documentation on the
special "localtime" value of this GUC (e.g.
https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-TIMEZONES
).
Shay
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-07-24 15:23:30 | Re: [PATCH] minor bugfix for pg_basebackup (9.6 ~ ) |
Previous Message | Alvaro Herrera | 2019-07-24 15:19:04 | Re: [bug fix] Produce a crash dump before main() on Windows |