pgsql: Fix WAL replay of truncate operations to cope with the

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix WAL replay of truncate operations to cope with the
Date: 2007-07-20 16:29:53
Message-ID: 20070720162953.76E569FC0C6@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Modified Files:
--------------
pgsql/src/backend/storage/smgr:
smgr.c (r1.104 -> r1.105)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/smgr/smgr.c.diff?r1=1.104&r2=1.105)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2007-07-20 16:29:59 pgsql: Fix WAL replay of truncate operations to cope with the
Previous Message Peter Eisentraut 2007-07-20 16:23:34 pgsql: Capitalize language key words in error messages