Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D4DF4476690 for ; Mon, 23 Sep 2002 23:44:45 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id EB91A47669D for ; Mon, 23 Sep 2002 23:44:44 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g8O3ib5D009824; Mon, 23 Sep 2002 23:44:37 -0400 (EDT) To: Bruce Momjian Cc: John Hasler , pgsql-sql@postgresql.org Subject: Re: [GENERAL] CURRENT_TIMESTAMP In-reply-to: <200209240317.g8O3HWK29571@candle.pha.pa.us> References: <200209240317.g8O3HWK29571@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 23 Sep 2002 23:17:32 -0400" Date: Mon, 23 Sep 2002 23:44:37 -0400 Message-ID: <9823.1032839077@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/292 X-Sequence-Number: 9569 Bruce Momjian writes: > 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 I object to both of those as phrased. If you have already unilaterally determined the design of this feature change, then go ahead and put that in. But I'd suggest o Revise current-time functions to allow access to statement start time which doesn't presuppose the vote about how to do it. regards, tom lane