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 8E2E6D1C97F for ; Wed, 28 Jan 2004 19:52:49 +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 67349-07 for ; Wed, 28 Jan 2004 15:52:19 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 6D6EDD1C9DF for ; Wed, 28 Jan 2004 15:52:17 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i0SJqFBk028649; Wed, 28 Jan 2004 14:52:15 -0500 (EST) To: cjwhite@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: Error seen when vacuuming pg_largeobject table In-reply-to: <000b01c3e5d7$b1224b90$57976b80@amer.cisco.com> References: <000b01c3e5d7$b1224b90$57976b80@amer.cisco.com> Comments: In-reply-to "Chris White \(cjwhite\)" message dated "Wed, 28 Jan 2004 11:48:20 -0800" Date: Wed, 28 Jan 2004 14:52:15 -0500 Message-ID: <28648.1075319535@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/257 X-Sequence-Number: 12120 > 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