BUG #16472: Bug in to_timestamp ?

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: jesvh(dot)cht(at)gmail(dot)com
Subject: BUG #16472: Bug in to_timestamp ?
Date: 2020-06-01 10:32:04
Message-ID: 16472-ab9037fa90ff70f3@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16472
Logged by: jesvh
Email address: jesvh(dot)cht(at)gmail(dot)com
PostgreSQL version: Unsupported/Unknown
Operating system: windows 10
Description:

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 ?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2020-06-01 12:02:23 Re: BUG #16472: Bug in to_timestamp ?
Previous Message Peter Geoghegan 2020-06-01 04:47:13 Re: Potential G2-item cycles under serializable isolation