Fix WAL replay of truncate operations to cope with the possibility that the
authorTom Lane <[email protected]>
Fri, 20 Jul 2007 16:30:05 +0000 (16:30 +0000)
committerTom Lane <[email protected]>
Fri, 20 Jul 2007 16:30:05 +0000 (16:30 +0000)
commit56b97a42a08ef686f0ac514c26e1f37da08b53d0
tree28d23083dd5a6175b1293045f68a96dedb22ea54
parentc9007b9dfc3428670eb40606c09e92a7ceeb3211
Fix WAL replay of truncate operations to cope with the possibility that the
truncated relation was deleted later in the WAL sequence.  Since replay
normally auto-creates a relation upon its first reference by a WAL log entry,
failure is seen only if the truncate entry happens to be the first reference
after the checkpoint we're restarting from; which is a pretty unusual case but
of course not impossible.  Fix by making truncate entries auto-create like
the other ones do.  Per report and test case from Dharmendra Goyal.
src/backend/storage/smgr/smgr.c