From: Bruce Momjian <pgman@candle.pha.pa.us>
To: John Hasler <john@dhh.gt.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Date: Mon, 23 Sep 2002 23:17:32 -0400 (EDT)
Message-ID: <200209240317.g8O3HWK29571@candle.pha.pa.us> (raw)
In-Reply-To: <8765ww9lh7.fsf@toncho.dhh.gt.org>
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
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: pgman@candle.pha.pa.us, john@dhh.gt.org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
In-Reply-To: <200209240317.g8O3HWK29571@candle.pha.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