aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2016-10-24 09:27:24 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2016-10-24 09:45:48 -0300
commit00f15338b234e5fd7cda2d7bf0ef8d9f29f6bf5f (patch)
treead797d9d3060bcb27675280bcce91324dbdd8e84 /src/backend/access/transam/commit_ts.c
parent7d80417d3dfc88b0c03b5c08a18b29f9d430e217 (diff)
downloadpostgresql-00f15338b234e5fd7cda2d7bf0ef8d9f29f6bf5f.tar.gz
postgresql-00f15338b234e5fd7cda2d7bf0ef8d9f29f6bf5f.zip
Preserve commit timestamps across clean restart
An oversight in setting the boundaries of known commit timestamps during startup caused old commit timestamps to become inaccessible after a server restart. Author and reporter: Julien Rouhaud Review, test code: Craig Ringer
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
-rw-r--r--src/backend/access/transam/commit_ts.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/backend/access/transam/commit_ts.c b/src/backend/access/transam/commit_ts.c
index a8d275f4d39..77465788254 100644
--- a/src/backend/access/transam/commit_ts.c
+++ b/src/backend/access/transam/commit_ts.c
@@ -844,6 +844,8 @@ SetCommitTsLimit(TransactionId oldestXact, TransactionId newestXact)
else
{
Assert(ShmemVariableCache->newestCommitTsXid == InvalidTransactionId);
+ ShmemVariableCache->oldestCommitTsXid = oldestXact;
+ ShmemVariableCache->newestCommitTsXid = newestXact;
}
LWLockRelease(CommitTsLock);
}