From: Josh Berkus <josh@agliodbs.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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 18:53:36 -0700
Message-ID: <200209231853.36530.josh@agliodbs.com> (raw)
In-Reply-To: <200209240037.g8O0bwM14523@candle.pha.pa.us>
References: <200209240037.g8O0bwM14523@candle.pha.pa.us>
Tom, Bruce,
> > 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.
>
> I was thinking 'transaction_timestamp' for the transaction start time, and
> current_timestamp for the statement start time. I would equate now()
> with current_timestamp.
May I point out that this will break compatibility for those used to the
current behavior?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, mkoi-pg@aon.at, aaron@MetroNY.com, rmello@cc.usu.edu, neilc@samurai.com
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
In-Reply-To: <200209231853.36530.josh@agliodbs.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