On Fri, Sep 30, 2011 at 3:57 PM, Simon Riggs <si...@2ndquadrant.com> wrote: > I think we should issue PANIC if the source is a critical rmgr, or > just WARNING if from a non-critical rmgr, such as indexes. > > Ideally, I think we should have a mechanism to allow indexes to be > marked corrupt. For example, a file that if present shows that the > index is corrupt and would be marked not valid. We can then create the > file and send a sinval message to force the index relcache to be > rebuilt showing valid set to false.
This seems not to be specific to the invalid-page table problem. All error cases from a non-critical rmgr should be treated not-PANIC. So I think that the idea should be implemented separately from the patch I've posted. Anyway what if read-only query accesses the index marked invalid? Just emit ERROR? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
