From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Difference in TO_TIMESTAMP results. |
Date: | 2018-09-18 08:32:14 |
Message-ID: | 874lenjjs9.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "Prabhat" == Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com> writes:
Prabhat> postgres[114552]=# select to_timestamp('15-07-84 23:30:32','dd-mm-yyyy
Prabhat> hh24:mi:ss');
Prabhat> to_timestamp
Prabhat> ------------------------------
Prabhat> 0084-07-15 23:30:32+05:53*:28*
Prabhat> (1 row)
Prabhat> My doubt is the *":28"* in timezone part in 2nd result, is it
Prabhat> expected ?
Yes, it's expected.
The timezone db as a general rule gives the actual local mean solar time
offset (down to seconds) at the reference location (Kolkata in this
case) as the UTC offset for times before the earliest historical data
known to the tzdb maintainers.
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | Oleksii Kliukin | 2018-09-18 09:25:40 | Re: [PATCH] Fix for infinite signal loop in parallel scan |
Previous Message | Tsunakawa, Takayuki | 2018-09-18 08:27:16 | RE: Changing the setting of wal_sender_timeout per standby |