Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Date: 2003-08-22 12:45:39
Message-ID: 200308221445.39573.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

> > 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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Frank van Vugt 2003-08-22 13:12:07 Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Previous Message Tom Lane 2003-08-22 12:27:13 Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12

Browse pgsql-hackers by date

  From Date Subject
Next Message Frank van Vugt 2003-08-22 13:12:07 Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Previous Message Tom Lane 2003-08-22 12:27:13 Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12