Re: clock_timestamp() and transaction_timestamp() function - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: clock_timestamp() and transaction_timestamp() function
Date
Msg-id 200312010254.hB12se322145@candle.pha.pa.us
Whole thread Raw
In response to Re: clock_timestamp() and transaction_timestamp() function  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: clock_timestamp() and transaction_timestamp() function  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Yes, user-visible.  They give additional current timestamp information.
> > transaction_timestamp() is the same as current_timestamp,
> > clock_timestamp is the same as gettimeofday(), and statement_timestamp
> > is a new one that shows statement start time.
>
> And what would be the point of that?

The goal was to give a unified API to the various time measurements:

    [clock|statement|transaction]_timestamp


--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: [BUGS] Bug in byteaout code in all PostgreSQL versions
Next
From: Bruce Momjian
Date:
Subject: Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: