Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 04E8E476102; Sun, 29 Sep 2002 15:41:56 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 34BAE47619E; Sun, 29 Sep 2002 15:41:55 -0400 (EDT) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1733821; Sun, 29 Sep 2002 12:42:13 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Tom Lane , Martijn van Oosterhout Subject: Re: [SQL] CURRENT_TIMESTAMP Date: Sun, 29 Sep 2002 12:43:45 -0700 X-Mailer: KMail [version 1.4] Cc: Bruce Momjian , Manfred Koizar , Roland Roberts , pgsql-sql@postgresql.org, pgsql-general@postgresql.org References: <20020929034706.GA6199@svana.org> <20020929041007.GB6199@svana.org> <8140.1033274153@sss.pgh.pa.us> In-Reply-To: <8140.1033274153@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209291243.45747.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/209 X-Sequence-Number: 31207 Tom, > I'd be happier with the whole thing if anyone had exhibited a convincing > use-case for statement timestamp. So far I've not seen any actual > examples of situations that are not better served by either transaction > timestamp or true current time. And the spec is perfectly clear that > CURRENT_TIMESTAMP does not mean true current time... Are we still planning on putting the three different versions of now() on t= he=20 TODO? I.e., now('transaction'), now('statement'), and now('immediate') With now() =3D now('transaction')? I still think it's a good idea, provided that we have some easy means to=20 determine now('statement'). --=20 -Josh Berkus Aglio Database Solutions San Francisco