Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4KCYQA06357 for ; Sun, 20 May 2001 08:34:26 -0400 (EDT) (envelope-from dev@archonet.com) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 151SPe-000J26-0W; Sun, 20 May 2001 13:34:22 +0100 Received: from archonet.com (ibook.archonet.com [192.168.1.32]) by mainbox.archonet.com (Postfix) with ESMTP id EBFFD13A38; Sun, 20 May 2001 13:30:29 +0100 (BST) Message-ID: <3B07B8C2.CD8A43EA@archonet.com> Date: Sun, 20 May 2001 13:29:54 +0100 From: Richard Huxton X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC) X-Accept-Language: en MIME-Version: 1.0 To: Cedar Cox Cc: pgsql-sql@postgresql.org Subject: Re: timestamp bug References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200105/216 X-Sequence-Number: 3033 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. you're not hitting an issue with clocks going forward/back for summertime/daylight savings time? - Richard Huxton