Re: clock_timestamp() and transaction_timestamp() function

From: Randolf Richardson <rr(at)8x(dot)ca>
To: pgsql-patches(at)postgresql(dot)org
Subject: Re: clock_timestamp() and transaction_timestamp() function
Date: 2003-11-30 19:45:08
Message-ID: Xns9443757E59CB3rr8xca@200.46.204.72
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

>> 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?

Bean counters love this stuff, especially during audits. =D

--
Randolf Richardson - rr(at)8x(dot)ca
Vancouver, British Columbia, Canada

Please do not eMail me directly when responding
to my postings in the newsgroups.

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Joe Conway 2003-11-30 20:57:32 Re: [BUGS] Bug in byteaout code in all PostgreSQL versions
Previous Message Tom Lane 2003-11-30 19:34:34 Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)