Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 5282E475469 for ; Mon, 25 Feb 2002 23:34:33 -0500 (EST) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.2) with HTTP id 810140; Mon, 25 Feb 2002 20:34:36 -0800 From: "Josh Berkus" Subject: Re: Timestamp operator error To: Tom Lane , "Josh Berkus" Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.2 Date: Mon, 25 Feb 2002 20:34:36 -0800 Message-ID: In-Reply-To: <27215.1014697694@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200202/377 X-Sequence-Number: 6799 Tom, > AFAICT, what's happening in 7.2 is that the closest-match operator > is "time + date", so it casts the interval to time (yielding 0 > hours), > and casts current_timestamp to date (yielding midnight today) > and adds. Any suggestions on an emergency fix for my (production) database? We've already seen a couple of major problems from this bug, and I'm worried that there will be others that I don't catch until it's too late. If I had the know-how, I'd fix the operator myself, but I don't. > I suspect this is good ammunition for the argument I've made from > time > to time that we have too many implicit conversions, not too few. Yes, definitely. Frankly, I'd prefer a large reduction in implicit conversions; I just got into trouble with the difference between current_timestamp and current_date that I would have caught much earlier if Postgres had disallowed the implicit conversion. -Josh ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco