Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Volatility of pg_xact_commit_timestamp() and pg_last_committed_xact()
Date: 2015-07-16 13:49:40
Message-ID: CAHGQGwEqjB9YNpZi6Nut2RVKmWU_CGsqYHPrKMWwtq0+ZwaSUg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2015-07-16 13:50:34 Re: TABLESAMPLE doesn't actually satisfy the SQL spec, does it?
Previous Message Fujii Masao 2015-07-16 13:41:37 Re: Re: [COMMITTERS] pgsql: Map basebackup tablespaces using a tablespace_map file