From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200209292127.g8TLRw219816@candle.pha.pa.us>
Subject: Re: [SQL] CURRENT_TIMESTAMP
In-Reply-To: <200209291347.49207.josh@agliodbs.com>
To: josh@agliodbs.com
Date: Sun, 29 Sep 2002 17:27:58 -0400 (EDT)
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Martijn van Oosterhout <kleptog@svana.org>,
	Manfred Koizar <mkoi-pg@aon.at>,
	Roland Roberts <roland@astrofoto.org>, pgsql-sql@postgresql.org,
	pgsql-general@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Josh Berkus wrote:
> Bruce,
> 
> > If we change CURRENT_TIMESTAMP to statement time, I don't think we need
> > now(""), but if we don't change it, I think we do --- somehow we should
> > allow users to access statement time.
> 
> I'd argue that we need the 3 kinds of now() regardless, just to limit user 
> confusion.   If we set things up as:
> 
> now() = transaction time
> current_timestamp = statement time
> timeofday() = exact time
> 
> That does give users access to all 3 timestamps, but using a competely 
> non-intuitive nomenclature.  It's likely that the three types of now() would 
> just be pointers to other time functions, but would provide nomenative 
> clarity.

I agree, having now() as a central place for time information is a good
idea.  Maybe we need to vote on these issues.

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