Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 06576475C60 for ; Mon, 23 Sep 2002 23:17:40 -0400 (EDT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 59B6A475B8F for ; Mon, 23 Sep 2002 23:17:38 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g8O3HWK29571; Mon, 23 Sep 2002 23:17:32 -0400 (EDT) From: Bruce Momjian Message-Id: <200209240317.g8O3HWK29571@candle.pha.pa.us> Subject: Re: [GENERAL] CURRENT_TIMESTAMP In-Reply-To: <8765ww9lh7.fsf@toncho.dhh.gt.org> To: John Hasler Date: Mon, 23 Sep 2002 23:17:32 -0400 (EDT) Cc: pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/288 X-Sequence-Number: 9565 John Hasler wrote: > Bruce Momjian writes: > > My point is that our current behavior may not be the most intuitive, and > > that most people may prefer a change. > > I would prefer a change. Yes, I guess that is my point, that we want to make transaction _and_ statement timestamp values available, but most people are going to use current_timestamp, and most people are going to assume it is statement time, not transaction time. Can I add TODO items for this: o Make CURRENT_TIMESTAMP/now() return statement start time o Add TRANSACTION_TIMESTAMP to return transaction start time -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073