Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id A12439FB80B for ; Wed, 24 Oct 2007 15:26:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30629-06-4 for ; Wed, 24 Oct 2007 15:26:48 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 78EF89FBCE3 for ; Wed, 24 Oct 2007 15:26:45 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9OIQY38010124; Wed, 24 Oct 2007 14:26:34 -0400 (EDT) To: Craig McElroy cc: PostgreSQL Admin List Subject: Re: Problem with PITR Past Particular WAL File In-reply-to: References: Comments: In-reply-to Craig McElroy message dated "Wed, 24 Oct 2007 11:46:52 -0500" Date: Wed, 24 Oct 2007 14:26:34 -0400 Message-ID: <10123.1193250394@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/239 X-Sequence-Number: 27153 Craig McElroy writes: >> Can you get a stack trace from the core dump reported here? > Certainly, how can that be obtained? $ gdb /path/to/postgres-executable /path/to/core-file gdb> bt gdb> quit If you don't find a corefile in $PGDATA (or wherever your system puts core files) then you probably need to restart the postmaster with "ulimit -c unlimited" to allow producing a core. If the "bt" output is just numbers and no symbols then it won't be of any use; in that case you'll need to find or build non-stripped Postgres executables. regards, tom lane