Thread: result of conversion to timestamp is shifted 1 minute back

Tomas Dobrovolny (tdobrovolny@certifis.cz) reports a bug with a severity of 1
The lower the number the more severe it is.

Short Description
result of conversion to timestamp is shifted 1 minute back

Long Description
When postgresql converts string representation of date to timestamp, he make one minute back error. Any insert or
updatewith string date representation damage real value of date! 

BUT if you use string date representation without time part, your data will be shifted one day back!!!

Tested on RedHat 7.0, PostgreSQL 7.0.3

Sample Code
select timestamp('2001-12-25 23:59:00+01') ;
gives 2001-12-25 23:58:00+01

select timestamp('2001-12-25 11:10:00+01') ;
gives 2001-12-25 11:09:00+01

select timestamp('2001-12-25') ;
gives 2001-12-24 23:59:00+01

No file was uploaded with this report

> When postgresql converts string representation of date to timestamp, he make one minute back error. Any insert or
updatewith string date representation damage real value of date! 
> BUT if you use string date representation without time part, your data will be shifted one day back!!!
> Tested on RedHat 7.0, PostgreSQL 7.0.3

We will need more details on your installation to be able to help, since
this is *not* reproducible on most systems. We've never heard of this
before!

                      - Thomas