From: Martijn van Oosterhout <kleptog@svana.org>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Manfred Koizar <mkoi-pg@aon.at>
Cc: Roland Roberts <roland@astrofoto.org>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [SQL] CURRENT_TIMESTAMP
Date: Sun, 29 Sep 2002 13:47:06 +1000
Message-ID: <20020929034706.GA6199@svana.org> (raw)
In-Reply-To: <200209290328.g8T3S3S17164@candle.pha.pa.us>
References: <cum2puo8d0clhbc5mvs6ju22bai3h2tood@4ax.com>
<200209290328.g8T3S3S17164@candle.pha.pa.us>
On Sat, Sep 28, 2002 at 11:28:03PM -0400, Bruce Momjian wrote:
>
> 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?
Well, I'd rather it didn't change at all. IMHO it's a feature, not a bug. In
any case, if it does get changed we'll have to go through the documentation
and work out whether we mean current_timestamp or now(). I think most people
actually want now().
Fortunatly where I work we only use now() so it won't really matter too
much. Is there a compelling reason to change?
> ---------------------------------------------------------------------------
>
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.
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: kleptog@svana.org, pgman@candle.pha.pa.us, mkoi-pg@aon.at, roland@astrofoto.org, pgsql-general@postgresql.org
Subject: Re: [SQL] CURRENT_TIMESTAMP
In-Reply-To: <20020929034706.GA6199@svana.org>
* 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