Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0QF5Zq12965 for ; Fri, 26 Jan 2001 10:05:35 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0QF5G929578; Fri, 26 Jan 2001 10:05:16 -0500 (EST) To: Christopher Sawtell cc: "Glen and Rosanne Eustace" , pgsql-sql@postgresql.org Subject: Re: Re: Problem with Dates In-reply-to: <01012621220800.13520@berty> References: <00ff01c0863e$c4ef8620$0101a8c0@godzone.net.nz> <20010124181731.G17481@thune.yy.com> <00d401c08729$077cc440$0101a8c0@godzone.net.nz> <01012621220800.13520@berty> Comments: In-reply-to Christopher Sawtell message dated "Fri, 26 Jan 2001 21:22:08 +1300" Date: Fri, 26 Jan 2001 10:05:15 -0500 Message-ID: <29575.980521515@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/379 X-Sequence-Number: 1052 Christopher Sawtell writes: > On Fri, 26 Jan 2001 12:46, Glen and Rosanne Eustace wrote: > [ ... ] >> template1=# select '31/12/2000'::date + '365 days'::timespan; >> ?column? >> ------------------------ >> 2002-01-01 00:00:00+13 <<<<<<<<<<< Wrong >> (1 row) > [ ... ] > I get the same result. This business of crooked dates in NZ summertime > is frequently because the rest of the world can't twig on to the notion that > it is possible to have GMT + 13, and do not take account of it in date/time > calculations. Could one of you try it in 7.1 (beta3 or later)? We've changed some details of the way daylight-savings transitions are handled in date-to-timestamp conversions, so I think this might be fixed now. It's worth checking anyway. Also, what do you get from '31/12/2000'::date::timestamp? regards, tom lane