Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 65B3E64FC01 for ; Thu, 25 Sep 2008 14:30:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61800-01 for ; Thu, 25 Sep 2008 14:30:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0EF8064FC20 for ; Thu, 25 Sep 2008 14:30:32 -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 m8PHUUci009026; Thu, 25 Sep 2008 13:30:30 -0400 (EDT) To: "BJ Taylor" cc: pgsql-admin@postgresql.org Subject: Re: missing chunk number 0 for toast value In-reply-to: <3d78fcfd0809250909h148daba8k2ad29e176d9a06fd@mail.gmail.com> References: <3d78fcfd0809241132y14a832cai8b32bc32e936699e@mail.gmail.com> <10862.1222287999@sss.pgh.pa.us> <3d78fcfd0809241446j326110c4p9907e04dbd10106b@mail.gmail.com> <5723.1222349048@sss.pgh.pa.us> <3d78fcfd0809250909h148daba8k2ad29e176d9a06fd@mail.gmail.com> Comments: In-reply-to "BJ Taylor" message dated "Thu, 25 Sep 2008 10:09:48 -0600" Date: Thu, 25 Sep 2008 13:30:30 -0400 Message-ID: <9025.1222363830@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/303 X-Sequence-Number: 30396 "BJ Taylor" writes: > Here are some recent logs from our system. Unfortunately, I didn't think to > grab the logs at the time I killed those processes, and now they are gone. > I found those processes by using ps, and then I killed them with a simple > kill *processid*. Here are samples of our current log files: Huh. That would have generated SIGTERM, which should at least mostly be safe. We did recently fix a couple of problems with cleanup after SIGTERM but they were both pretty low-probability risks. Anyway, you've definitely got issues now: > PANIC: right sibling's left-link doesn't match: block 175337 links to > 243096 instead of expected 29675 in index "dbmail_headervalue_3" Try reindexing that index, and any other ones that you see complaints about. > You also asked how it is being unstable. It drops connections seemingly at > random. The error received when a connection is dropped is the following: > WARNING: terminating connection because of crash of another server process Well, that's just the fallout from a PANIC in some other session; if you weren't watching the session that actually crashed, you need to look in the postmaster log to see what went wrong. regards, tom lane