| From: | Shay Rojansky <roji(at)roji(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "localtime" value in TimeZone |
| Date: | 2019-07-25 16:51:25 |
| Message-ID: | CADT4RqCqCc=6vzq+nw9bUZP-ZR_G6ohqBkqbnpgKwsgnUYosrA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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 that this was a distribution-level mechanism - I
understand the situation better now.
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"?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dent John | 2019-07-25 16:52:01 | Re: add_path() for Path without InitPlan: cost comparison vs. Paths that require one |
| Previous Message | Bruce Momjian | 2019-07-25 16:46:52 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |