Re: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()
Date: 2015-07-22 18:05:41
Message-ID: CA+TgmoaGpd=YvhLyf8MNDnJW56U=pROgdPrFxyeLhc2Qx+LPGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 16, 2015 at 9:49 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> Volatilities of pg_xact_commit_timestamp() and pg_last_committed_xact()
> are now STABLE. But ISTM that those functions can return different results
> even within a single statement. So we should change the volatilities of them
> to VOLATILE?

Sounds right to me.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-07-22 18:10:01 Re: [PATCH] postgres_fdw extension support
Previous Message Robert Haas 2015-07-22 18:03:58 Re: Eliminating CREATE INDEX comparator TID tie-breaker overhead