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

From: "ir(dot) F(dot)T(dot)M(dot) van Vugt bc(dot)" <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12
Date: 2003-08-21 18:56:14
Message-ID: 200308212056.14850.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Giacomo Cariello 2003-08-21 19:19:56 Re: repalloc bug
Previous Message Stephan Szabo 2003-08-21 17:52:24 Re: postgresql 7.3.2 bug on date '1901-12-13' and '1901-12

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2003-08-21 19:22:21 Re: Can't find thread on Linux memory overcommit
Previous Message elein 2003-08-21 18:16:48 Re: Need concrete "Why Postgres not MySQL" bullet list