Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 454872E0377 for ; Mon, 17 Mar 2008 23:32:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 47819-06 for ; Mon, 17 Mar 2008 23:32:34 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id CA3862E0361 for ; Mon, 17 Mar 2008 23:32:34 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2I2WW0L007207; Mon, 17 Mar 2008 22:32:32 -0400 (EDT) To: "Chadwick Horn" cc: pgsql-sql@postgresql.org Subject: Re: postgres server crashes unexpectedly In-reply-to: <71EB10BF787341C28A47F33667D0D8FC@ToshibaLaptop> References: <71EB10BF787341C28A47F33667D0D8FC@ToshibaLaptop> Comments: In-reply-to "Chadwick Horn" message dated "Mon, 17 Mar 2008 18:20:15 -0700" Date: Mon, 17 Mar 2008 22:32:31 -0400 Message-ID: <7206.1205807551@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/94 X-Sequence-Number: 30422 "Chadwick Horn" writes: > PANIC: corrupted item pointer: offset = 0, size = 0 > LOG: autovacuum process (PID 3037) was terminated by signal 6 Hmm ... the only instances of that error text are in PageIndexTupleDelete and PageIndexMultiDelete, so we can fairly safely say that you have a partially zeroed-out page in some index somewhere. If that's the only damage then you're in luck: you can recover by reindexing. What I'd do is turn off autovacuum and instead do a manual VACUUM VERBOSE to see where it crashes; then you could just reindex the one problem table instead of the whole database. You ought to look into why this happened, too. Since you've provided precisely 0 context about PG version or platform, it's hard to speculate about that ... regards, tom lane