X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EB64BD1B4D1 for ; Thu, 29 Jan 2004 06:55:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 80636-03 for ; Thu, 29 Jan 2004 02:54:43 -0400 (AST) Received: from ind-iport-1.cisco.com (ind-iport-1-sec.cisco.com [64.104.129.9]) by svr1.postgresql.org (Postfix) with ESMTP id 481F0D1B85F for ; Thu, 29 Jan 2004 02:54:36 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 29 Jan 2004 17:54:57 +0530 Received: from cjwhitew2k02 (sjc-vpn1-1031.cisco.com [10.21.100.7]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0T6sWus024219; Wed, 28 Jan 2004 22:54:34 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Wed, 28 Jan 2004 22:54:34 -0800 Message-ID: <003901c3e634$c321dc90$57976b80@amer.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <28648.1075319535@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/263 X-Sequence-Number: 12126 Tom, It happened again. After doing the reindex, I did a vacuum full on the pg_largeobject table. This time I did not get the TUPLE INDEX error but the server terminated at the end of the vacuum command. The backend is still running even though I get the error message: aesop=# vacuum full verbose pg_largeobject; NOTICE: --Relation pg_largeobject-- blocks 21 NOTICE: Pages 21: Changed 0, reaped 19, Empty 0, New 0; Tup 69: Vac 749, Keep/VTL 0/0, UnUsed 181, MinLen 16, MaxLen 2092; Re-using: Free/Avail. Space 146752/146752; EndEmpty/Avail. Pages 0/21. CPU 0.00s/0.00u sec elapsed 0.00 sec. NOTICE: Index pg_largeobject_loid_pn_index: Pages 2; Tuples 69: Deleted 0. CPU 0.00s/0.00u sec elapsed 0.00 sec. server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. It consistently happens when I try to vacuum full the pg_largeobject table. Is there anything I can get from the system to determine what is happening? Chris -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Wednesday, January 28, 2004 11:52 AM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table > Got it to happen again after a power fail. Here is the logs this time > with verbose. Hm, those backend crashes should have left core dumps; can you get a stack trace from the core? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html