Excerpts from Jeff Amiel's message of mar jun 08 09:26:25 -0400 2010: > Not looking for help...just putting some data out there. > > 2 previous crashes caused by corrupt slony indexes > > http://archives.postgresql.org/pgsql-general/2010-02/msg00022.php > > http://archives.postgresql.org/pgsql-general/2009-12/msg01172.php > > New one yesterday. > > Jun 7 15:05:01 db-1 postgres[9334]: [ID 748848 local0.crit] [3989781-1] > 2010-06-07 15:05:01.087 CDT 9334PANIC: right sibling 169 of block 168 is > not next child of 249 in index "sl_seqlog_idx"
I've seen this problem (and others) in a high-load environment. Not Slony related though. I wrote a small tool to check btree index files for consistency problems such as this one, by parsing pg_filedump output. I've seen strange things such as index pointers pointing to pages that shouldn't have been pointed to; mismatching sibling pointers; and others. Do you have a copy of the broken index file? -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
