Thread: Date Representation Bug. Timezone and update on an already posted as #208 reportbug

Gianfranco Pesce (g.pesce@hotbrain.it) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Date Representation Bug. Timezone and update on an already posted as #208 reportbug

Long Description
The problem of date representation of 22/05/1977 and 28/05/1978 is
related with time zone.

The system is a Linux RedHat 6.2 (also tested on Redhat 7.0 and 7.1) with postegresql 6.5 and 7.1.

ONLY 22/05/1977 and 28/05/1978 are bad recorded into the db. This dates are stored (or retrieved) as 21/05/1977 ans
27/05/1978respectively. ALL other date correcly stored. 

If I modify my timezone from MET (DayLight Saving Time Enabled) to PDT
the bug disappears.



Sample Code
echo $PGDATESTYLE
SQL,EUROPEAN

test=> create table pippo (d date);
CREATE
test=> insert into pippo values ('22/05/1977');
INSERT 629024 1
test=> insert into pippo values ('28/05/1978');
INSERT 629025 1
test=> insert into pippo values ('30/10/1964');
INSERT 629026 1

test=> select * from pippo;
d
------------
21/05/1977
27/05/1978
30/10/1964
(3 rows)

test=> select * from pippo where d = '22/05/1977';
d
------------
21/05/1977
(1 rows)

No file was uploaded with this report

pgsql-bugs@postgresql.org writes:
> The problem of date representation of 22/05/1977 and 28/05/1978 is
> related with time zone.

What do you get if you coerce the funny dates to timestamp, eg,

    select '22/05/1977'::date::timestamp;

            regards, tom lane