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 A3D67D1D1A4 for ; Thu, 29 Jan 2004 17:04:19 +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 16360-03 for ; Thu, 29 Jan 2004 13:03:48 -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 BF2AFD1D26D for ; Thu, 29 Jan 2004 13:03:46 -0400 (AST) Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 30 Jan 2004 04:04:02 +0530 Received: from cjwhitew2k02 (dhcp-128-107-151-87.cisco.com [128.107.151.87]) by india-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0TH3Wus007778; Thu, 29 Jan 2004 09:03:34 -0800 (PST) Reply-To: From: "Chris White (cjwhite)" To: "'Tom Lane'" Cc: Subject: Re: Error seen when vacuuming pg_largeobject table Date: Thu, 29 Jan 2004 09:03:35 -0800 Message-ID: <006501c3e689$d6f00cb0$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: <22231.1075389003@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/271 X-Sequence-Number: 12134 Sorry I meant to say the server terminated the connection as indicated by the error message but the server is still running and there is no core (This time I enabled them). Chris -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane Sent: Thursday, January 29, 2004 7:10 AM To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table "Chris White \(cjwhite\)" writes: > 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. Can you enable core dumps and get a stack trace? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match