Shay Rojansky writes:
> I followed the conversations you linked to, and disagreements seem to be
> mostly about other aspects of timezone selection. Does it make sense to
> have a limited, restricted conversation specifically about avoiding
> "localtime"?
I've tried to kick-start the other thread
> Yeah, this is something that some tzdb packagers do --- they put a
> "localtime" file into /usr/share/zoneinfo that is a symlink or hard link
> to the active zone file, and then initdb tends to seize on that as being
> the shortest available spelling of the active zone.
I see, I wasn't aware tha
Shay Rojansky writes:
> 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
