]> granicus.if.org Git - postgresql/commit
Fix WAL replay of truncate operations to cope with the possibility that the
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 20 Jul 2007 16:29:59 +0000 (16:29 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 20 Jul 2007 16:29:59 +0000 (16:29 +0000)
commit85506ffbd51e15dffbd307e4d1060cfffb24c9e0
tree5a543ec996874f02f61662d251e241aa1092a864
parent8208fb4b6305bfdd9b89faa6b70fc58b59338d53
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