| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Palle Girgensohn <girgen(at)pingpong(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Chris Withers <chris(at)withers(dot)org>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "pgsql\(at)freebsd(dot)org" <pgsql(at)freebsd(dot)org> |
| Subject: | Re: here does postgres take its timezone information from? |
| Date: | 2019-11-17 21:10:03 |
| Message-ID: | 87zhgu1adu.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>>> Ugh. It doesn't have the old backward compatibility names like
>>> US/Pacific installed by default, which is a problem if that's what
>>> initdb picked for your cluster (or you've stored references to any
>>> of those names in other ways).
>> One quick fix is to revert the change. Tom thinks this is not reason
>> to revert. Would it be enough to edit the postgresql.conf to use the
>> correct "modern" name for US/Pacific (PST?)? In rhar case, an update
>> note might be sufficient?
Tom> I think the "official" name of that zone is America/Los_Angeles.
Tom> But initdb might seize on the US/Pacific alias, if available,
And now you know why I have been saying for so many years that initdb
should use the official names!
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Sergio Borgonovo | 2019-11-18 00:29:44 | Re: porting horde to Postgresql 12, dropped pg_attrdef |
| Previous Message | Adrian Klaver | 2019-11-17 18:31:45 | Re: Function's execute overhead reducing |