Re: [GENERAL] CURRENT_TIMESTAMP - Mailing list pgsql-sql

From Bruce Momjian
Subject Re: [GENERAL] CURRENT_TIMESTAMP
Date
Msg-id 200209290328.g8T3S3S17164@candle.pha.pa.us
Whole thread Raw
In response to Re: [GENERAL] CURRENT_TIMESTAMP  (Manfred Koizar <mkoi-pg@aon.at>)
Responses Re: [GENERAL] CURRENT_TIMESTAMP  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-sql
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

pgsql-sql by date:

Previous
From: "Andrew G. Hammond"
Date:
Subject: Re: SQL formatter?
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] CURRENT_TIMESTAMP