From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200209290328.g8T3S3S17164@candle.pha.pa.us>
Subject: Re: [SQL] CURRENT_TIMESTAMP
In-Reply-To: <cum2puo8d0clhbc5mvs6ju22bai3h2tood@4ax.com>
To: Manfred Koizar <mkoi-pg@aon.at>
Date: Sat, 28 Sep 2002 23:28:03 -0400 (EDT)
Cc: 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


OK, we have two db's returning statement start time, and Oracle 8 not
having CURRENT_TIMESTAMP.

Have we agreed to make CURRENT_TIMESTAMP statement start, and now()
transaction start?  Is this an open item or TODO item?

---------------------------------------------------------------------------

Manfred Koizar wrote:
> On Tue, 24 Sep 2002 17:56:51 -0400 (EDT), Bruce Momjian
> <pgman@candle.pha.pa.us> wrote:
> >Can you run a test:
> >
> >	BEGIN;
> >	SELECT CURRENT_TIMESTAMP;
> >	wait 5 seconds
> >	SELECT CURRENT_TIMESTAMP;
> >
> >Are the two times the same?
> 
> MS SQL 7:
> 	begin transaction
> 	insert into tst values (CURRENT_TIMESTAMP)
> 	-- wait
> 	insert into tst values (CURRENT_TIMESTAMP)
> 	commit
> 	select * from tst
> 
> 	t                           
> 	--------------------------- 
> 	2002-09-24 09:49:58.777
> 	2002-09-24 09:50:14.100
> 
> Interbase 6:
> 	SQL> select current_timestamp from rdb$database;
> 
> 	=========================
> 	2002-09-24 22:30:13.0000
> 
> 	SQL> select current_timestamp from rdb$database;
> 
> 	=========================
> 	2002-09-24 22:30:18.0000
> 
> 	SQL> commit;
> 
> Servus
>  Manfred
> 

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