Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B6FD92E3C01 for ; Tue, 22 Jan 2008 08:50:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 66105-01-3 for ; Tue, 22 Jan 2008 08:50:10 -0400 (AST) Received: from proton.planetargon.com (proton.planetargon.com [198.145.115.11]) by postgresql.org (Postfix) with ESMTP id E6AFF2E02B3 for ; Tue, 22 Jan 2008 08:43:18 -0400 (AST) Received: by proton.planetargon.com (Postfix, from userid 502) id 31F37983337; Tue, 22 Jan 2008 04:42:52 -0800 (PST) Received: from [10.0.1.200] (c-67-165-16-168.hsd1.ct.comcast.net [67.165.16.168]) by proton.planetargon.com (Postfix) with ESMTP id 42A45835793; Tue, 22 Jan 2008 04:42:31 -0800 (PST) In-Reply-To: <4795A3B0.3010505@cat.co.za> References: <4795A3B0.3010505@cat.co.za> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <794E6600-42A8-41A2-822D-080E19F9F0CC@seespotcode.net> Cc: pgsql-sql@postgresql.org Content-Transfer-Encoding: 7bit From: Michael Glaesemann Subject: Re: TIMESTAMP comparison problem Date: Tue, 22 Jan 2008 07:42:20 -0500 To: Stuart Brooks X-Mailer: Apple Mail (2.753) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/174 X-Sequence-Number: 30027 On Jan 22, 2008, at 3:05 , Stuart Brooks wrote: > If I reduce the precision to 3 for the timestamps it appears to > work although it makes me nervous. With float timestamps, you're fooling yourself if you think those numbers past the decimal are reliable. > Should I just recompile to use integer datetimes? I would like to > have at least microsecond precision. Well, you can't get better than microsecond precision with timestamps in Postgres. And the only way you can rely on that level of precision is to compile with --enable-integer-datetimes. Michael Glaesemann grzm seespotcode net