From: Tom Lane <tgl@sss.pgh.pa.us>
To: Litao Wu <litaowu@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: reindex and copy - deadlock?
Date: Tue, 08 Jun 2004 13:51:08 -0400
Message-ID: <4464.1086717068@sss.pgh.pa.us> (raw)
In-Reply-To: <20040608172542.90818.qmail@web13123.mail.yahoo.com>
References: <20040608172542.90818.qmail@web13123.mail.yahoo.com>
Litao Wu <litaowu@yahoo.com> writes:
> I will use gdb next time. What's this right way to
> get info as postgres owner?
$ gdb /path/to/postgres
gdb> attach PID-of-backend-process
gdb> bt
gdb> quit
You might try this for practice on any idle backend; it shouldn't affect
the state of the backend, except for freezing it while you issue the
commands.
If "bt" gives you just a list of numbers and no symbolic information,
then it won't be much help; you'll need to rebuild the backend with
debugging information so that we can make some sense of the trace.
regards, tom lane
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, litaowu@yahoo.com
Subject: Re: reindex and copy - deadlock?
In-Reply-To: <4464.1086717068@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