From b2a667b9ee8ba8d54e92fddcb0ed8d30651be595 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Tue, 20 Jan 2009 18:59:37 +0000 Subject: Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should be used instead of the normal exclusive lock, and make WAL redo functions responsible for calling RestoreBkpBlocks(). They know better what kind of a lock they need. At the moment, this just moves things around with no functional change, but makes the hot standby patch that's under review cleaner. --- src/backend/access/gist/gistxlog.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'src/backend/access/gist/gistxlog.c') diff --git a/src/backend/access/gist/gistxlog.c b/src/backend/access/gist/gistxlog.c index b6d76a1f47..672d714e01 100644 --- a/src/backend/access/gist/gistxlog.c +++ b/src/backend/access/gist/gistxlog.c @@ -8,7 +8,7 @@ * Portions Copyright (c) 1994, Regents of the University of California * * IDENTIFICATION - * $PostgreSQL: pgsql/src/backend/access/gist/gistxlog.c,v 1.31 2009/01/01 17:23:35 momjian Exp $ + * $PostgreSQL: pgsql/src/backend/access/gist/gistxlog.c,v 1.32 2009/01/20 18:59:36 heikki Exp $ *------------------------------------------------------------------------- */ #include "postgres.h" @@ -394,9 +394,10 @@ void gist_redo(XLogRecPtr lsn, XLogRecord *record) { uint8 info = record->xl_info & ~XLR_INFO_MASK; - MemoryContext oldCxt; + RestoreBkpBlocks(lsn, record, false); + oldCxt = MemoryContextSwitchTo(opCtx); switch (info) { -- cgit v1.2.1