Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Eisentraut
Subject Re: clock_timestamp() and transaction_timestamp() function
Date
Msg-id Pine.LNX.4.44.0311301838270.11144-100000@peter.localdomain
Whole thread Raw
In response to Re: clock_timestamp() and transaction_timestamp() function  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: clock_timestamp() and transaction_timestamp() function  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Tree view 
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@gmx.net

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: clock_timestamp() and transaction_timestamp() function
Next
From: Bruce Momjian
Date:
Subject: Re: clock_timestamp() and transaction_timestamp() function