Excerpts from Nikhil Sontakke's message of mié mar 16 08:51:00 -0300 2011: > Hi, > > > To summarize, as I see it - the zeroed out block 523 should have been > > the second left-most leaf and should have pointed out to 522. Thus > > re-establishing the index chain > > > > 524 -> 523 -> 522 -> 277 -> ... > > > >> Was there a machine restart in the picture as well? > > > > It seems there might have been a machine restart involved too. So I > guess even WAL writing could have been impacted.
Maybe the filesystem decided to fill a couple of FS pages (one PG page) with zeroes on recovery due to believing that it wasn't fsynced at the time of the crash. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
