Re: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()
Date: 2015-07-30 18:22:33
Message-ID: 20150730182233.GS2441@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> Robert Haas wrote:
> > 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.
>
> Will fix.

Fix pushed.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-07-30 18:26:34 Re: security labels on databases are bad for dump & restore
Previous Message Andres Freund 2015-07-30 18:14:22 Re: LWLock deadlock and gdb advice