Re: bug of recovery?
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-09-27T07:00:50Z
Lists: pgsql-hackers
On Tue, Sep 27, 2011 at 6:54 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > I think you're mixing this up with the multi-page page split operations in > b-tree. This is different from that. What the "invalid_page_tab" is for is > the situation where you for example, insert to a page on table X, and later > table X is dropped, and then you crash. On WAL replay, you will see the > insert record, but the file for the table doesn't exist, because the table > was dropped. In that case we skip the insert, note what happened in > invalid_page_tab, and move on with recovery. When we see the later record to > drop the table, we know it was OK that the file was missing earlier. But if > we don't see it before end of recovery, we PANIC, because then the file > should've been there. OK, yes, I see. Thanks. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services