Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f4MEbpA87830 for ; Tue, 22 May 2001 10:37:51 -0400 (EDT) (envelope-from pgsql-sql-owner@postgresql.org) Received: from news.tht.net (news.hub.org [216.126.91.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4KJvYA50793 for ; Sun, 20 May 2001 15:57:34 -0400 (EDT) (envelope-from news@news.tht.net) Received: (from news@localhost) by news.tht.net (8.11.1/8.11.1) id f4KJWBb53279 for pgsql-sql@postgresql.org; Sun, 20 May 2001 15:32:11 -0400 (EDT) (envelope-from news) From: Alexander Dederer X-Newsgroups: comp.databases.postgresql.sql Subject: Re: timestamp bug Date: Sun, 20 May 2001 23:34:11 +0400 Organization: Hub.Org Networking Services (http://www.hub.org) Lines: 18 Message-ID: <9e963p$1jqh$1@news.tht.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: scrappy@hub.org User-Agent: KNode/0.4 To: pgsql-sql@postgresql.org X-Archive-Number: 200105/239 X-Sequence-Number: 3056 Cedar Cox wrote: > > There appears to be a bug in timestamp/interval addition. It happens in > both PG version 7.0.2 and 7.1. There is a duplicate day (2001 Sep 07) and > a missing day (2002 Apr 04). I discovered this by accident when I asked > the interface I'm writing for a 365 day long calendar.. Interestingly, > the missing day thing (second example) doesn't happen if only adding a few > days (like the first example). I didn't go into detail to find the point > at which it does happen. IMN1=# SELECT version(); version --------------------------------------------------------------- PostgreSQL 7.1.1 on i686-pc-linux-gnu, compiled by GCC 2.95.3 (1 row) And all right work. Try new version.