On Mon, Mar 20, 2017 at 11:28 PM, Robert Haas <robertmh...@gmail.com> wrote: > On Sat, Mar 18, 2017 at 5:42 PM, Jeff Janes <jeff.ja...@gmail.com> wrote: >> Isn't HEAP2_CLEAN only issued before an intended HOT update? (Which then >> can't leave the block as all visible or all frozen). I think the issue is >> here is HEAP2_VISIBLE or HEAP2_FREEZE_PAGE. Am I reading this correctly, >> that neither of those ever update the FSM, regardless of FPI? > > Yes, updates to the FSM are never logged. Forcing replay of > HEAP2_FREEZE_PAGE to update the FSM might be a good idea. >
I think I was missing something. I imaged your situation is that FPI is replayed during crash recovery after the crashed server vacuums the page and marked it as all-frozen. But this situation is also resolved by that solution. Regards, -- Masahiko Sawada 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
