Thread: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()
Hi, 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? Regards, -- Fujii Masao
On Thu, Jul 16, 2015 at 9:49 AM, Fujii Masao <masao.fujii@gmail.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
Robert Haas wrote: > On Thu, Jul 16, 2015 at 9:49 AM, Fujii Masao <masao.fujii@gmail.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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Alvaro Herrera wrote: > Robert Haas wrote: > > On Thu, Jul 16, 2015 at 9:49 AM, Fujii Masao <masao.fujii@gmail.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