X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id A2C5CD1CB0F for ; Wed, 3 Mar 2004 23:19:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28214-06 for ; Wed, 3 Mar 2004 19:19:22 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 527F3D1CAF6 for ; Wed, 3 Mar 2004 19:19:14 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i23NJJoq019030; Wed, 3 Mar 2004 18:19:19 -0500 (EST) To: Steve Crawford Cc: DHS Webmaster , pgsql-admin Subject: Re: bizarre AGE behaviour In-reply-to: <200403031000.05524.scrawford@pinpointresearch.com> References: <40461395.5324CFEE@dhs-club.com> <200403031000.05524.scrawford@pinpointresearch.com> Comments: In-reply-to Steve Crawford message dated "Wed, 03 Mar 2004 10:00:05 -0800" Date: Wed, 03 Mar 2004 18:19:19 -0500 Message-ID: <19029.1078355959@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/17 X-Sequence-Number: 12587 Steve Crawford writes: > US Daylight Saving Time starts this year on April 4 when 0200 jumps to > 0300. The answers PostgreSQL gave are correct. I suspect what the OP wants is non-timezone-aware behavior, which he could get by casting the inputs of age() to timestamp without time zone. As written the system is preferring to interpret them as timestamp with time zone. Also, if what's really wanted is just resolution to the day level, the date subtraction operator might be a lot better choice than age() anyway. regression=# select '06-01-04'::date - '04-01-04'::date; ?column? ---------- 61 (1 row) regards, tom lane