Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should
authorHeikki Linnakangas <heikki@enterprisedb.com>
Tue, 20 Jan 2009 18:59:37 +0000 (18:59 +0000)
committerHeikki Linnakangas <heikki@enterprisedb.com>
Tue, 20 Jan 2009 18:59:37 +0000 (18:59 +0000)
commit5403a7851823fd2686a3f29d12208414eb6dd1b0
tree4592784c29dc8dd0d331eae766608665475253c0
parent290fd9389d980ec1d70732f12257a60c23701d5a
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.
15 files changed:
src/backend/access/gin/ginxlog.c
src/backend/access/gist/gistxlog.c
src/backend/access/heap/heapam.c
src/backend/access/nbtree/nbtxlog.c
src/backend/access/transam/clog.c
src/backend/access/transam/multixact.c
src/backend/access/transam/xact.c
src/backend/access/transam/xlog.c
src/backend/access/transam/xlogutils.c
src/backend/catalog/storage.c
src/backend/commands/dbcommands.c
src/backend/commands/sequence.c
src/backend/commands/tablespace.c
src/backend/storage/freespace/freespace.c
src/include/access/xlog.h