pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brendan Duddridge <brendan@clickspace.com>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Recovery will take 10 hours
Date: Thu, 20 Apr 2006 17:19:48 -0400
Message-ID: <105.1145567988@sss.pgh.pa.us> (raw)
In-Reply-To: <47C1F053-EC91-4AEB-9F0B-B538716145D6@clickspace.com>
References: <85A15B2E-F59C-4FEF-82D4-61F48ABDCDE5@clickspace.com>
	<29439.1145564220@sss.pgh.pa.us>
	<47C1F053-EC91-4AEB-9F0B-B538716145D6@clickspace.com>

Brendan Duddridge <brendan@clickspace.com> writes:
> Do you mean do a kill -QUIT on the postgres process in order to  
> generate a stack trace?

Not at all!  I'm talking about tracing the kernel calls it's making.
Depending on your platform, the tool for this is called strace,
ktrace, truss, or maybe even just trace.  With strace you'd do
something like

	strace -p PID-of-process 2>outfile
	... wait 30 sec or so ...
	control-C

Not sure about the APIs for the others but they're probably roughly
similar ... read the man page ...

			regards, tom lane



view thread (21+ messages)  latest in thread

Message-ID: <105.1145567988@sss.pgh.pa.us>
Permalink:  ../105.1145567988@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/105.1145567988@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, brendan@clickspace.com
  Subject: Re: Recovery will take 10 hours
  In-Reply-To: <105.1145567988@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox