Skip site navigation (1) Skip section navigation (2)

Re: diagnosing a db crash - server exit code 2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Robert Burgholzer <rburghol(at)vt(dot)edu>, "Burgholzer, Robert (DEQ)" <Robert(dot)Burgholzer(at)deq(dot)virginia(dot)gov>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: diagnosing a db crash - server exit code 2
Date: 2011-10-03 23:10:45
Message-ID: 23681.1317683445@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Joe Conway <mail(at)joeconway(dot)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

In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2011-10-04 03:53:11
Subject: Re: index bloat on partial index 8.4
Previous:From: Julius TuskenisDate: 2011-10-03 18:17:17
Subject: Re: commiting transaction from outside

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group