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 e5608cW93604 for ; Mon, 5 Jun 2000 20:08:38 -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 UAA14266; Mon, 5 Jun 2000 20:08:33 -0400 (EDT) To: Fabrice Scemama cc: pgsql-sql@postgresql.org Subject: Re: Vacuum problem in my system ? In-reply-to: <393C0F30.86E652AA@ximmo.ftd.fr> References: <393BE6CA.43073AB3@ximmo.ftd.fr> <12539.960221996@sss.pgh.pa.us> <393C0F30.86E652AA@ximmo.ftd.fr> Comments: In-reply-to Fabrice Scemama message dated "Mon, 05 Jun 2000 21:36:00 +0100" Date: Mon, 05 Jun 2000 20:08:33 -0400 Message-ID: <14263.960250113@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/51 Fabrice Scemama writes: > No core dump could be found within the data/base/* directories. Hm. When I've seen a backend crash without leaving a core file, it's usually because the backend ran up against the system's per-process memory limit. (Many kernels seem to choose not to drop a core file when they kill a process for memory exhaustion.) You could check that theory by watching the process's memory usage with "top". Anything in the postmaster log? regards, tom lane