Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id 8B226475ED1; Mon, 23 Sep 2002 13:06:08 -0400 (EDT)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by postgresql.org (Postfix) with ESMTP
	id DBECD475E22; Mon, 23 Sep 2002 13:06:07 -0400 (EDT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g8NH5g5D022828;
	Mon, 23 Sep 2002 13:05:42 -0400 (EDT)
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	Aaron Held <aaron@MetroNY.com>, Roberto Mello <rmello@cc.usu.edu>,
	Neil Conway <neilc@samurai.com>, pgsql-sql@postgresql.org,
	pgsql-general@postgresql.org
Subject: Re: [SQL] Monitoring a Query 
In-reply-to: <0meuousc373fdokv3bbke116jsbkpakno2@4ax.com> 
References: <21724.1032793386@sss.pgh.pa.us>
	<200209231506.g8NF6JP13779@candle.pha.pa.us>
	<0meuousc373fdokv3bbke116jsbkpakno2@4ax.com>
Comments: In-reply-to Manfred Koizar <mkoi-pg@aon.at>
	message dated "Mon, 23 Sep 2002 19:01:01 +0200"
Date: Mon, 23 Sep 2002 13:05:42 -0400
Message-ID: <22827.1032800742@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200209/1008
X-Sequence-Number: 30589

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