| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timeofday() and clock_timestamp() produce different results when casting to timestamptz |
| Date: | 2013-03-23 15:16:26 |
| Message-ID: | 22506.1364051786@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> Seems the time zone info still thinks Moscow time is being setting
> forward an hour for DST when in fact the time remains constant through
> the year.
I think the discrepancy is between this in timezone/data/europe:
Zone Europe/Moscow 2:30:20 - LMT 1880
2:30 - MMT 1916 Jul 3 # Moscow Mean Time
2:30:48 Russia %s 1919 Jul 1 2:00
3:00 Russia MSK/MSD 1922 Oct
2:00 - EET 1930 Jun 21
3:00 Russia MSK/MSD 1991 Mar 31 2:00s
2:00 Russia EE%sT 1992 Jan 19 2:00s
3:00 Russia MSK/MSD 2011 Mar 27 2:00s
4:00 - MSK
and this in timezone/tznames/Default:
MSD 14400 D # Moscow Daylight Time
# (Europe/Moscow)
MSK 10800 # Moscow Time
# (Europe/Moscow)
We really need to figure out a way to update the tznames data
automatically, or at least notice when it's become inconsistent with
the underlying Olson database.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasen Betts | 2013-03-23 22:35:36 | Re: Can't terminate hung COPY |
| Previous Message | News Subsystem | 2013-03-23 14:13:48 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicholas White | 2013-03-23 17:00:25 | Request for Patch Feedback: Lag & Lead Window Functions Can Ignore Nulls |
| Previous Message | Adrian Klaver | 2013-03-23 14:09:54 | Re: timeofday() and clock_timestamp() produce different results when casting to timestamptz |