Received: from ximmo.ftd.fr (XIMMO.FTD.FR [212.11.11.75]) by hub.org (8.10.1/8.10.1) with SMTP id e55IokW65342 for ; Mon, 5 Jun 2000 14:50:46 -0400 (EDT) Received: (qmail 23572 invoked from network); 5 Jun 2000 20:36:00 -0000 Received: from ximmo.ftd.fr (212.11.11.75) by ximmo.ftd.fr with SMTP; 5 Jun 2000 20:36:00 -0000 Message-ID: <393C0F30.86E652AA@ximmo.ftd.fr> Date: Mon, 05 Jun 2000 21:36:00 +0100 From: Fabrice Scemama X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: pgsql-sql@postgresql.org Subject: Re: Vacuum problem in my system ? References: <393BE6CA.43073AB3@ximmo.ftd.fr> <12539.960221996@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200006/46 No core dump could be found within the data/base/* directories. The cron is executed by user root, but on my system root is a PostgreSQL superuser. Tom Lane wrote: > > 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