Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2L5R0t15025 for ; Wed, 21 Mar 2001 00:27:00 -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 f2L5Qrt21513; Wed, 21 Mar 2001 00:26:53 -0500 (EST) To: Daryl Herzmann cc: pgsql-sql@postgresql.org Subject: Re: Maybe a Bug, maybe bad SQL In-reply-to: References: Comments: In-reply-to Daryl Herzmann message dated "Mon, 19 Mar 2001 13:46:10 -0600" Date: Wed, 21 Mar 2001 00:26:53 -0500 Message-ID: <21510.985152413@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/410 X-Sequence-Number: 2078 Daryl Herzmann writes: > akrherz=# create table test (day date); > CREATE > akrherz=# insert into test values('2000_04_02'); > INSERT 13166281 1 > akrherz=# insert into test values('2000_04_01'); > INSERT 13166282 1 > akrherz=# insert into test values('2000_04_03'); > INSERT 13166283 1 Would that be a daylight-savings transition date in your timezone? If so, this is a known date-to-timestamp conversion bug. It's fixed for 7.1. regards, tom lane