Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12 - Mailing list pgsql-bugs

From Frank van Vugt
Subject Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Date
Msg-id 200308221445.39573.ftm.van.vugt@foxi.nl
Whole thread Raw
In response to Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> > anything I can verify on that one to help?
>
> "show time zone"?

free4testing=# show time zone;
 TimeZone
----------
 unknown
(1 row)

free4testing=# select now();
              now
-------------------------------
 2003-08-22 14:36:17.994049+02
(1 row)



The latter is what I meant by 'it seems to be using the correct timezone'.

V7.3.3 on the other Slackware machine shows exactly the same output.

V7.4cvs on the machine where I originally tested setting TZ explicitly had TZ
set to nothing after the test, so as per docs it reverted to UTC. After
unsetting TZ and restarting the postmaster I got the same old behaviour back
(my 19 minute wide timezone) with output equal to the one above.






Frank.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Next
From: Frank van Vugt
Date:
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12