From: Andrew Sullivan <andrew@libertyrms.info>
To: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: [SQL] [GENERAL] CURRENT_TIMESTAMP
Date: Thu, 3 Oct 2002 18:03:19 -0400
Message-ID: <20021003180319.Z18497@mail.libertyrms.com> (raw)
In-Reply-To: <200210032018.g93KI8110524@candle.pha.pa.us>
References: <11772.1033421161@sss.pgh.pa.us>
<200210032018.g93KI8110524@candle.pha.pa.us>
On Thu, Oct 03, 2002 at 04:18:08PM -0400, Bruce Momjian wrote:
>
> So, we have a couple of decisions to make:
>
> Should CURRENT_TIMESTAMP be changed to "statement arrival time"?
> Should now() be changed the same way?
> If not, should now() and CURRENT_TIMESTAMP return the same type of
> value?
>
> One idea is to change CURRENT_TIMESTAMP to "statement arrival time", and
> leave now() as transaction start time.
A disadvantage to this, as I see it, is that users may have depended on
the traditional Postgres behaviour of time "freezing" in transaction.
You always had to select timeofday() for moving time. I can see an
advantage in making what Postgres does somewhat more like what other
people do (as flat-out silly as some of that seems to be). Still, it
looks to me like the present CURRENT_TIMESTAMP implementation is at
least as much like the spec as anyone else's implementation, and more
like the spec than many of them. So I'm still not clear on what
problem the change is going to fix, especially since it breaks with
traditional behaviour.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
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: andrew@libertyrms.info, pgsql-hackers@postgreSQL.org
Subject: Re: [SQL] [GENERAL] CURRENT_TIMESTAMP
In-Reply-To: <20021003180319.Z18497@mail.libertyrms.com>
* 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