Skip site navigation (1) Skip section navigation (2)

Re: Additional current timestamp values

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>
Subject: Re: Additional current timestamp values
Date: 2006-03-20 23:00:06
Message-ID: 200603210000.07477.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian wrote:
> Rather than applying the above patch, I have implemented this TODO
> with the attached patch:
>
> 	* Add transaction_timestamp(), statement_timestamp(),
> clock_timestamp() functionality

The most common complaint that I recall is that current_timestamp 
returns the transaction timestamp rather than the statement timestamp, 
which is what many expect.  How does your patch address that?

Do we really need clock_timestamp?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-03-20 23:02:06
Subject: Re: Additional current timestamp values
Previous:From: Bruce MomjianDate: 2006-03-20 22:34:24
Subject: Additional current timestamp values

pgsql-patches by date

Next:From: Tom LaneDate: 2006-03-20 23:01:24
Subject: Re: Removal of backward-compatibility docs mentions
Previous:From: Bruce MomjianDate: 2006-03-20 22:34:24
Subject: Additional current timestamp values

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group