From 74afe40629a844602b983f8c1719971a767a8ceb Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 20 Jul 2007 16:30:12 +0000 Subject: [PATCH] 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 | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/backend/storage/smgr/smgr.c b/src/backend/storage/smgr/smgr.c index 9ef216dfa1..095f758f63 100644 --- a/src/backend/storage/smgr/smgr.c +++ b/src/backend/storage/smgr/smgr.c @@ -811,6 +811,14 @@ smgr_redo(XLogRecPtr lsn, XLogRecord *record) reln = smgropen(xlrec->rnode); + /* + * Forcibly create relation if it doesn't exist (which suggests that + * it was dropped somewhere later in the WAL sequence). As in + * XLogOpenRelation, we prefer to recreate the rel and replay the + * log as best we can until the drop is seen. + */ + smgrcreate(reln, false, true); + /* Can't use smgrtruncate because it would try to xlog */ /* -- 2.39.5