pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.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:52:55 -0400 (EDT)
Message-ID: <200209240352.g8O3qtJ03739@candle.pha.pa.us> (raw)
In-Reply-To: <9823.1032839077@sss.pgh.pa.us>

Tom Lane wrote:
> 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.

OK, I am still just throwing out ideas.  I am not sure we even have
enough people who want statement_timestamp to put it in TODO. I do think
we have a standards issue.

My personal opinion is that most people think current_timestamp and
now() are statement start time, not transaction start time.  In the past
we have told them the standard requires that but now I think we are not
even sure if that is correct.

So, I have these concerns:

	our CURRENT_TIMESTAMP may not be standards compliant
	even if it is, it is probably not returning the value most people want
	most people don't know it is returning the transaction start time

So, we can just throw the TODO item you mentioned above with a question
mark, or we can try to figure out what to return for CURRENT_TIMESTAMP,
now(), and perhaps create a TRANSACTION_TIMESTAMP.

So, do people want to discuss it or should we just throw it in TODO with
a question mark?

-- 
  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



view thread (61+ messages)  latest in thread

Message-ID: <200209240352.g8O3qtJ03739@candle.pha.pa.us>
Permalink:  ../200209240352.g8O3qtJ03739@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200209240352.g8O3qtJ03739@candle.pha.pa.us

 · 

reply

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, tgl@sss.pgh.pa.us, john@dhh.gt.org
  Subject: Re: [GENERAL] CURRENT_TIMESTAMP
  In-Reply-To: <200209240352.g8O3qtJ03739@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