From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: John Hasler <john@dhh.gt.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Date: Mon, 23 Sep 2002 23:44:37 -0400
Message-ID: <9823.1032839077@sss.pgh.pa.us> (raw)
In-Reply-To: <200209240317.g8O3HWK29571@candle.pha.pa.us>
References: <200209240317.g8O3HWK29571@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, john@dhh.gt.org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
In-Reply-To: <9823.1032839077@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox