Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id CBEB72E035F for ; Tue, 4 Dec 2007 13:56:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 61574-04 for ; Tue, 4 Dec 2007 13:56:23 -0400 (AST) Received: from mail.int.journyx.com (mail.journyx.com [66.219.41.227]) by postgresql.org (Postfix) with ESMTP id 5D06C2E01D9 for ; Tue, 4 Dec 2007 13:56:24 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.int.journyx.com (Postfix) with ESMTP id 75DB23F272D for ; Tue, 4 Dec 2007 11:56:21 -0600 (CST) X-Virus-Scanned: amavisd-new at Received: from mail.int.journyx.com ([127.0.0.1]) by localhost (mail.int.journyx.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RWlwcurOiLbb for ; Tue, 4 Dec 2007 11:56:15 -0600 (CST) Received: from whitneys (dhcp-100-201.int.journyx.com [192.168.100.201]) by mail.int.journyx.com (Postfix) with ESMTP id 00BAA3F276D for ; Tue, 4 Dec 2007 11:02:51 -0600 (CST) From: "Scott Whitney" To: Subject: PANIC: right sibling Date: Tue, 4 Dec 2007 11:03:15 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-index: Acg2l48tVEh+X+y4Q5SU5yg6AHnRGg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Message-Id: <20071204170252.00BAA3F276D@mail.int.journyx.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/9 X-Sequence-Number: 27526 I don't really understand the postings I've found on this issue. This has been going on for quite some time, but now that I'm regularly vacuuming this db, I was looking for any info on how to fix this problem...I don't even know enough about it to know what to include in this message. This is the last output of: vacuumdb -f -z -v rt3 vacuumdb: vacuuming of database "rt3" failed: PANIC: right sibling is not next child in "tickets1" server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.