From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
---|---|
To: | jesvh(dot)cht(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16472: Bug in to_timestamp ? |
Date: | 2020-06-01 12:02:23 |
Message-ID: | CAPpHfdu-dxL7d45vEuEK7YrL1Jqi-GL+kZprAi9vHXf2N1NKRg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi!
On Mon, Jun 1, 2020 at 1:38 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> Hi :
> I execute a update SQL as below :
> update Table1 set date1=to_timestamp('19790701000000', 'YYYYMMDDHH24MISS')
> where .....
>
> date1 is a timestamp type column, the result in DB is 1979-07-01 01:00:00
> where come from that '01' hour ?
>
> but if set to other date value, it works correct ....
> Is it a special bug ?
It's likely related to clock shift in your timezone.
What is your timezone and PostgreSQL version? You can figure out them
using following queries.
show timezone;
select version();
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2020-06-01 13:52:06 | BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) |
Previous Message | PG Bug reporting form | 2020-06-01 10:32:04 | BUG #16472: Bug in to_timestamp ? |