Re: clock_timestamp() and transaction_timestamp() function

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Wang Mike <itlist(at)msn(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: clock_timestamp() and transaction_timestamp() function
Date: 2003-11-30 18:51:25
Message-ID: Pine.LNX.4.44.0311301951120.11144-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

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?

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2003-11-30 18:56:06 Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)
Previous Message Peter Eisentraut 2003-11-30 18:46:46 Re: Making pg_dump cvs friendly