From: Tom Lane <tgl@sss.pgh.pa.us>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Aaron Held <aaron@MetroNY.com>
Cc: Roberto Mello <rmello@cc.usu.edu>
Cc: Neil Conway <neilc@samurai.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-general@postgresql.org
Subject: Re: [SQL] Monitoring a Query
Date: Mon, 23 Sep 2002 13:05:42 -0400
Message-ID: <22827.1032800742@sss.pgh.pa.us> (raw)
In-Reply-To: <0meuousc373fdokv3bbke116jsbkpakno2@4ax.com>
References: <21724.1032793386@sss.pgh.pa.us>
<200209231506.g8NF6JP13779@candle.pha.pa.us>
<0meuousc373fdokv3bbke116jsbkpakno2@4ax.com>
Manfred Koizar <mkoi-pg@aon.at> writes:
> This has been discussed before and I know I'm going to get flamed for
> this, but IMHO having now() (which is a synonym for CURRENT_TIMESTAMP)
> return the start time of the current transaction is a bug, or at least
> it is not conforming to the standard.
As you say, it's been discussed before. We concluded that the spec
defines the behavior as implementation-dependent, and therefore we
can pretty much do what we want.
If you want exact current time, there's always timeofday().
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, mkoi-pg@aon.at, pgman@candle.pha.pa.us, aaron@MetroNY.com, rmello@cc.usu.edu, neilc@samurai.com, pgsql-general@postgresql.org
Subject: Re: [SQL] Monitoring a Query
In-Reply-To: <22827.1032800742@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