Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 340A447603C
	for <pgsql-sql@postgresql.org>; Mon, 23 Sep 2002 21:52:15 -0400 (EDT)
Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250])
	by postgresql.org (Postfix) with ESMTP id 95BFA475CB1
	for <pgsql-sql@postgresql.org>; Mon, 23 Sep 2002 21:52:14 -0400 (EDT)
Received: from [66.219.92.2] (HELO chocolate-mousse)
	by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9)
	with ESMTP id 1658341; Mon, 23 Sep 2002 18:52:17 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: Bruce Momjian <pgman@candle.pha.pa.us>,
	Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Date: Mon, 23 Sep 2002 18:53:36 -0700
X-Mailer: KMail [version 1.4]
Cc: Manfred Koizar <mkoi-pg@aon.at>, Aaron Held <aaron@MetroNY.com>,
	Roberto Mello <rmello@cc.usu.edu>, Neil Conway <neilc@samurai.com>,
	pgsql-sql@postgresql.org
References: <200209240037.g8O0bwM14523@candle.pha.pa.us>
In-Reply-To: <200209240037.g8O0bwM14523@candle.pha.pa.us>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200209231853.36530.josh@agliodbs.com>
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200209/284
X-Sequence-Number: 9561


Tom, Bruce,

> > A possible compromise is to dissociate now() and current_timestamp,
> > allowing the former to be start of transaction and the latter to be
> > start of client command.
>=20
> I was thinking 'transaction_timestamp' for the transaction start time, and
> current_timestamp for the statement start time.  I would equate now()
> with current_timestamp.

May I point out that this will break compatibility for those used to the=20
current behavior?


--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco