postgresql/src/backend/access
Heikki Linnakangas b2a667b9ee 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.
2009-01-20 18:59:37 +00:00
..
common Simplify the writing of amoptions routines by introducing a convenience 2009-01-12 21:02:15 +00:00
gin Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should 2009-01-20 18:59:37 +00:00
gist Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should 2009-01-20 18:59:37 +00:00
hash Change the reloptions machinery to use a table-based parser, and provide 2009-01-05 17:14:28 +00:00
heap Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should 2009-01-20 18:59:37 +00:00
index Update copyright for 2009. 2009-01-01 17:24:05 +00:00
nbtree Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should 2009-01-20 18:59:37 +00:00
transam Add a new option to RestoreBkpBlocks() to indicate if a cleanup lock should 2009-01-20 18:59:37 +00:00
Makefile Refactor backend makefiles to remove lots of duplicate code 2008-02-19 10:30:09 +00:00