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

From ir. F.T.M. van Vugt bc.
Subject Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Date
Msg-id 200308212056.14850.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  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Responses Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
List pgsql-bugs
> > > Hmm, I just got my machine to give a similar failure mode with
> > > a slightly wacky input.

Will you allow me to add to this wackyness with the following on CVS tip from
this morning:

free4testing=# select version();
                             version
------------------------------------------------------------------
 PostgreSQL 7.4beta1 on i586-pc-linux-gnu, compiled by GCC 2.95.3
(1 row)

free4testing=# select timestamptz '1901/12/13 23:59:59.99999';
        timestamptz
---------------------------
 1901-12-13 23:59:59.99999
(1 row)

free4testing=# select timestamptz '1901/12/13 23:59:59.999999999';
        timestamptz
---------------------------
 1901-12-14 00:19:00+00:19
(1 row)

free4testing=# select timestamptz '2001/12/14 0:0:0';
      timestamptz
------------------------
 2001-12-14 00:00:00+01
(1 row)


Yes, that's a new timezone on the second case, indeed, probably a kind of
'floating' one ;-)





Frank.

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Next
From: Jonathan Gardner
Date:
Subject: Renaming table doesn't rename primary key index or serial sequences