Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e55GK6O31840 for ; Mon, 5 Jun 2000 12:20:06 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id MAA12542; Mon, 5 Jun 2000 12:19:56 -0400 (EDT) To: Fabrice Scemama cc: pgsql-sql@postgresql.org Subject: Re: Vacuum problem in my system ? In-reply-to: <393BE6CA.43073AB3@ximmo.ftd.fr> References: <393BE6CA.43073AB3@ximmo.ftd.fr> Comments: In-reply-to Fabrice Scemama message dated "Mon, 05 Jun 2000 18:43:38 +0100" Date: Mon, 05 Jun 2000 12:19:56 -0400 Message-ID: <12539.960221996@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/43 Fabrice Scemama writes: > [ vacuum appears to be coredumping ] That's odd ... not so much that vacuum could be failing, which is probably a garden-variety bug; but it sounds like the postmaster is failing to do the system restart that it should do after one of the backends fails. Is there anything showing up in the postmaster log when this happens? As for tracking the immediate vacuum problem, the failed backend should have left a core dump file in the database directory (.../data/base/DBNAME/core). Can you get a backtrace from that with gdb? Something like gdb path/to/postgres path/to/core bt quit should do. regards, tom lane