pgsql: Improve API of GenericXLogRegister().

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve API of GenericXLogRegister().
Date: 2016-04-12 15:42:12
Message-ID: E1aq0SC-0000gx-LQ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve API of GenericXLogRegister().

Rename this function to GenericXLogRegisterBuffer() to make it clearer
what it does, and leave room for other sorts of "register" actions in
future. Also, replace its "bool isNew" argument with an integer flags
argument, so as to allow adding more flags in future without an API
break.

Alexander Korotkov, adjusted slightly by me

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5713f03973e26ad6df6df5ac8b9efa0123d68062

Modified Files
--------------
contrib/bloom/blinsert.c | 10 +++++-----
contrib/bloom/blutils.c | 9 +++++----
contrib/bloom/blvacuum.c | 4 ++--
doc/src/sgml/generic-wal.sgml | 32 +++++++++++++++++--------------
src/backend/access/transam/generic_xlog.c | 10 ++++++----
src/include/access/generic_xlog.h | 7 +++++--
6 files changed, 41 insertions(+), 31 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-04-12 15:52:01 Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.
Previous Message Tom Lane 2016-04-12 15:14:13 pgsql: In generic WAL application and replay, ensure page "hole" is alw