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:59 |
Message-ID: | 20070720162959.4BAB69FC0C6@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.
Tags:
----
REL8_2_STABLE
Modified Files:
--------------
pgsql/src/backend/storage/smgr:
smgr.c (r1.101.2.1 -> r1.101.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/smgr/smgr.c.diff?r1=1.101.2.1&r2=1.101.2.2)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-07-20 16:30:05 | pgsql: Fix WAL replay of truncate operations to cope with the |
Previous Message | Tom Lane | 2007-07-20 16:29:53 | pgsql: Fix WAL replay of truncate operations to cope with the |