pgsql: Fix commit timestamp initialization - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Fix commit timestamp initialization
Date
Msg-id E1a7RXH-0001kN-R4@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix commit timestamp initialization

This module needs explicit initialization in order to replay WAL records
in recovery, but we had broken this recently following changes to make
other (stranger) scenarios work correctly.  To fix, rework the
initialization sequence so that it always takes place before WAL replay
commences for both master and standby.

I could have gone for a more localized fix that just added a "startup"
call for the master server, but it seemed better to restructure the
existing callers as well so that the whole thing made more sense.  As a
drawback, there is more control logic in xlog.c now than previously, but
doing otherwise meant passing down the ControlFile flag, which seemed
uglier as a whole.

This also meant adding a check to not re-execute ActivateCommitTs if it
had already been called.

Reported by Fujii Masao.

Backpatch to 9.5.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/69e7235c93e2965cc0e17186bd044e4c54997c19

Modified Files
--------------
src/backend/access/transam/commit_ts.c |   39 ++++++++++++++++++++++----------
src/backend/access/transam/xlog.c      |   22 ++++++++++--------
src/include/access/commit_ts.h         |    2 +-
3 files changed, 40 insertions(+), 23 deletions(-)


pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: pgsql: Fix commit timestamp initialization
Next
From: Tom Lane
Date:
Subject: pgsql: Still more fixes for planner's handling of LATERAL references.