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

Re: Additional current timestamp values

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-patches(at)postgresql(dot)org, Brendan Jurd <direvus(at)gmail(dot)com>
Subject: Re: Additional current timestamp values
Date: 2006-03-20 23:02:06
Message-ID: 200603202302.k2KN26J07336@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Peter Eisentraut wrote:
> 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?

No, we believe the standard requires it.

> Do we really need clock_timestamp?

Yes, because timeofday() returns a unix text string.  Some people do
want a wallclock current timestamp.

-- 
  Bruce Momjian   http://candle.pha.pa.us
  SRA OSS, Inc.   http://www.sraoss.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

Next:From: Neil ConwayDate: 2006-03-20 23:05:02
Subject: Re: Additional current timestamp values
Previous:From: Peter EisentrautDate: 2006-03-20 23:00:06
Subject: Re: Additional current timestamp values

pgsql-patches by date

Next:From: Bruce MomjianDate: 2006-03-20 23:03:10
Subject: Re: Removal of backward-compatibility docs mentions
Previous:From: Tom LaneDate: 2006-03-20 23:01:24
Subject: Re: Removal of backward-compatibility docs mentions

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