Tom Lane <[EMAIL PROTECTED]> writes: > I think what's happened here is that VACUUM FULL moved the only tuple > off page 1 of the relation, then truncated off page 1, and now > heap_update_redo is panicking because it can't find page 1 to replay the > move. Curious that we've not seen a case like this before, because it > seems like a generic hazard for WAL replay.
This sounds familiar http://archives.postgresql.org/pgsql-hackers/2005-05/msg01369.php -- greg ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
