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 17:39:05
Message-ID: Pine.LNX.4.44.0311301838270.11144-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian writes:

> We have started 7.5 development so we can now work with you to complete
> this item. Your question was what does statement_timestamp() show.
> That has been discussed and it is a little tricky. The idea is that is
> should be start of a single statement that arrives from the user or is
> requestd by a client. However, this gets muddled because SPI can issue
> queries and plpgsql functions can too.

Are these supposed to be user-visible functions? What are they supposed
to do?

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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-11-30 17:42:31 Re: clock_timestamp() and transaction_timestamp() function
Previous Message Bruce Momjian 2003-11-30 17:26:47 Re: clock_timestamp() and transaction_timestamp() function