Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 6E490475DC8; Sun, 29 Sep 2002 16:45:59 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 7C0FA475C85; Sun, 29 Sep 2002 16:45:58 -0400 (EDT) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1733867; Sun, 29 Sep 2002 13:46:17 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Bruce Momjian Subject: Re: [SQL] CURRENT_TIMESTAMP Date: Sun, 29 Sep 2002 13:47:49 -0700 X-Mailer: KMail [version 1.4] Cc: Tom Lane , Martijn van Oosterhout , Manfred Koizar , Roland Roberts , pgsql-sql@postgresql.org, pgsql-general@postgresql.org References: <200209292038.g8TKcbR15198@candle.pha.pa.us> In-Reply-To: <200209292038.g8TKcbR15198@candle.pha.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209291347.49207.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/224 X-Sequence-Number: 31222 Bruce, > If we change CURRENT_TIMESTAMP to statement time, I don't think we need > now(""), but if we don't change it, I think we do --- somehow we should > allow users to access statement time. I'd argue that we need the 3 kinds of now() regardless, just to limit user= =20 confusion. If we set things up as: now() =3D transaction time current_timestamp =3D statement time timeofday() =3D exact time That does give users access to all 3 timestamps, but using a competely=20 non-intuitive nomenclature. It's likely that the three types of now() woul= d=20 just be pointers to other time functions, but would provide nomenative=20 clarity. --=20 -Josh Berkus Aglio Database Solutions San Francisco