Re: clock_timestamp() and transaction_timestamp() function

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Wang Mike <itlist(at)msn(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: clock_timestamp() and transaction_timestamp() function
Date: 2003-12-01 15:50:29
Message-ID: Pine.LNX.4.44.0312011649130.23890-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Tom Lane writes:

> This is a nonstarter, as is the previous proposal to have a single
> function with an explicit parameter that selects the behavior. The
> reason is that any such function would have to be treated as completely
> non-optimizable.

Why? We would just need to ensure that the mode cannot be changed at
critical times.

> I am unconvinced that anyone has really proven the need for
> statement_timestamp,

Compatibility with other database systems might be one (if it is
accessible through current_timestamp).

--
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-12-01 15:50:55 Re: clock_timestamp() and transaction_timestamp() function
Previous Message Bruce Momjian 2003-12-01 15:36:51 Re: clock_timestamp() and transaction_timestamp() function