Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 945C9B5DBC4
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon,  3 Oct 2011 20:11:02 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 93472-01-2
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Mon,  3 Oct 2011 23:10:55 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 28B15B5DCC2
	for <pgsql-admin@postgresql.org>; Mon,  3 Oct 2011 20:10:52 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p93NAjGK023682;
	Mon, 3 Oct 2011 19:10:45 -0400 (EDT)
To: Joe Conway <mail@joeconway.com>
cc: Robert Burgholzer <rburghol@vt.edu>, "Burgholzer,
	Robert (DEQ)" <Robert.Burgholzer@deq.virginia.gov>,
	Scott Marlowe <scott.marlowe@gmail.com>, pgsql-admin@postgresql.org
Subject: Re: diagnosing a db crash - server exit code 2 
In-reply-to: <4E89F0CF.9080807@joeconway.com> 
References: 
 <B6C40D17104BEF47B1CB85623CDFAC6357BE26@COVMSGCES-EMB13.cov.virginia.gov>
	<4E7CDCA6.6060803@joeconway.com>
	<B6C40D17104BEF47B1CB85623CDFAC6357BE27@COVMSGCES-EMB13.cov.virginia.gov>
	<CAOR=d=3BoU+CRsOLVWY7a870cdQ2uc9KQcBA43cT-5J1_CKhow@mail.gmail.com>
	<B6C40D17104BEF47B1CB85623CDFAC6357BE2A@COVMSGCES-EMB13.cov.virginia.gov>
	<4E7CF42E.2050904@joeconway.com>
	<B6C40D17104BEF47B1CB85623CDFAC6357BE2F@COVMSGCES-EMB13.cov.virginia.gov>
	<CACT-NGKP07Ku5y7=JdOFDx+PYv-5w70CAv=N8yuc4w2HeSotHQ@mail.gmail.com>
	<4E84AB05.1050106@joeconway.com>
	<B6C40D17104BEF47B1CB85623CDFAC6302DD473B@COVMSGCES-EMB13.cov.virginia.gov>
	<CACT-NGJNW92jOFfp9N4u9APrmV0WjnJwg1ix37-yESWWSCDO2g@mail.gmail.com>
	<4E89F0CF.9080807@joeconway.com>
Comments: In-reply-to Joe Conway <mail@joeconway.com>
	message dated "Mon, 03 Oct 2011 10:28:47 -0700"
Date: Mon, 03 Oct 2011 19:10:45 -0400
Message-ID: <23681.1317683445@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.404 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504
X-Spam-Level: 
X-Archive-Number: 201110/12
X-Sequence-Number: 38464

Joe Conway <mail@joeconway.com> writes:
> On 10/03/2011 10:10 AM, Robert Burgholzer wrote:
>> FWIW - I am currently trying this while tracing the process that I
>> assume is the postmaster (/usr/bin/postgres -D /home/postgres/data),
>> since this process number indicates that it was recently restarted -
>> although the other PG processes, writer, wal writer, autovacuum, stats
>> collector all have their older pids indicating that they still survive.

> Sounds like you are attaching to the wrong process. Try something like
> the below...

No need to guess about it ... use "select pg_backend_pid();" and then
attach to that process.  (BTW, the "postmaster" is the parent process.
The one you want to debug is a backend.)

			regards, tom lane