From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: josh@agliodbs.com, Manfred Koizar <mkoi-pg@aon.at>
Cc: Aaron Held <aaron@MetroNY.com>
Cc: Roberto Mello <rmello@cc.usu.edu>
Cc: Neil Conway <neilc@samurai.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Date: Mon, 23 Sep 2002 20:32:52 -0400
Message-ID: <8770.1032827572@sss.pgh.pa.us> (raw)
In-Reply-To: <200209240011.g8O0BVL11014@candle.pha.pa.us>
References: <200209240011.g8O0BVL11014@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I see what you are saying now --- that even single user statements can
> trigger multiple statements, so you would have to say transaction start
> time is time the user query starts. I can see how that seems a little
> arbitrary. However, don't we have separate paths for user queries and
> queries sent as part of a rule?
We could use "time of arrival of the latest client command string",
if we wanted to do something like this. My point is that that very
arbitrarily assumes that those are the significant points within a
transaction, and that the client has no need to send multiple commands
that want to insert the same timestamp into different tables. This is
an unwarranted assumption about the client's control structure, IMHO.
A possible compromise is to dissociate now() and current_timestamp,
allowing the former to be start of transaction and the latter to be
start of client command.
regards, tom lane
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: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, mkoi-pg@aon.at, aaron@MetroNY.com, rmello@cc.usu.edu, neilc@samurai.com
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
In-Reply-To: <8770.1032827572@sss.pgh.pa.us>
* 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