X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 2D2909DC836 for ; Mon, 2 Jan 2006 18:34:26 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 87524-08 for ; Mon, 2 Jan 2006 18:34:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id CB2CF9DC80F for ; Mon, 2 Jan 2006 18:34:21 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k02MYLIg012865; Mon, 2 Jan 2006 17:34:22 -0500 (EST) To: warren little cc: pgsql-admin@postgresql.org Subject: Re: Emergency - Need assistance In-reply-to: <1136240683.16094.40.camel@sharp> References: <1136228730.16094.12.camel@sharp> <11864.1136232604@sss.pgh.pa.us> <1136233928.16094.33.camel@sharp> <12399.1136237657@sss.pgh.pa.us> <1136240683.16094.40.camel@sharp> Comments: In-reply-to warren little message dated "Mon, 02 Jan 2006 15:24:43 -0700" Date: Mon, 02 Jan 2006 17:34:21 -0500 Message-ID: <12864.1136241261@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.061 required=5 tests=[AWL=0.061] X-Spam-Score: 0.061 X-Spam-Level: X-Archive-Number: 200601/27 X-Sequence-Number: 20115 warren little writes: > The dump/restore failed even with the zero_damaged_pages=true. > The the logfile (postgresql-2006-01-02_130023.log) > did not have much in the way of useful info. I've attached the section > of the logfile around the time of the crash. I cannot find any sign of > a core file. Where might the core dump have landed? It would typically go into $PGDATA (if you're using 8.1) or some subdirectory thereof (if you're using an older release). There are some platforms such as OS X that put core files in a special directory /core so check for that too. If you're not finding any corefile then the most likely bet is that the postmaster has been launched under "ulimit -c 0" which forbids dropping a corefile. (This seems to be the default environment under many Linuxen.) I'd suggest adding "ulimit -c unlimited" to the postmaster start script you're using, restarting the postmaster, and repeating the dump to cause the crash again. regards, tom lane