Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fABH0om88892 for ; Sun, 11 Nov 2001 12:00:50 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id fABH0dc20173; Sun, 11 Nov 2001 12:00:39 -0500 (EST) To: Sharmad Naik cc: pgsql-sql@postgresql.org Subject: Re: error in postgresql In-reply-to: <20011111211315.A630@goatelecom.com> References: <3bde7ee4.753.0@punweb01> <2628.1004478416@sss.pgh.pa.us> <20011111211315.A630@goatelecom.com> Comments: In-reply-to Sharmad Naik message dated "Sun, 11 Nov 2001 21:13:15 +0530" Date: Sun, 11 Nov 2001 12:00:39 -0500 Message-ID: <20170.1005498039@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/152 X-Sequence-Number: 5536 Sharmad Naik writes: > When I gave a search for core file I didn't seems to > exist.pg_dump didnot create the core file pg_dump isn't coring, it's the backend. Backend core files normally appear in $PGDATA/base/whicheverdb/. If you don't see one there, it's likely because you started the postmaster under "ulimit -c 0" (this seems to be the default for init-script-started processes on at least some Linux distros :-(). Restart it with "ulimit -c unlimited" and try again. regards, tom lane