From: Andrew Sullivan <andrew@libertyrms.info>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [SQL] [GENERAL] CURRENT_TIMESTAMP
Date: Thu, 3 Oct 2002 19:58:39 -0400
Message-ID: <20021003195839.A16643@mail.libertyrms.com> (raw)
In-Reply-To: <15244.1033686573@sss.pgh.pa.us>
References: <200210032215.g93MFx823428@candle.pha.pa.us>
<15244.1033686573@sss.pgh.pa.us>
On Thu, Oct 03, 2002 at 07:09:33PM -0400, Tom Lane wrote:
> statement-arrival time. (I like the idea of a parameterized version of
> now() to provide a consistent interface to all three functionalities.)
I like this, too. I think it'd be probably useful. But. . .
> pride of place to statement-arrival time. In the end, I think that
> transaction-start time is the most commonly useful and safest variant,
. . .I also think this is true. If I'm doing a bunch of database
operations in one transaction, there is a remarkably good argument
that they happened "at the same time". After all, the marked passage
of time is probably just an unfortunate side effect of the inability
of my database can't process things instantaneously.
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: <20021003195839.A16643@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