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: Wed, 30 Jun 2004 15:33:02 -0400
Message-ID: <13105.1088623982@sss.pgh.pa.us> (raw)
In-Reply-To: <20040630184518.89025.qmail@web13122.mail.yahoo.com>
References: <20040630184518.89025.qmail@web13122.mail.yahoo.com>
Litao Wu <litaowu@yahoo.com> writes:
> Since there are multiple databases and
> there are 170 postgres processes this morning,
> 60 of them are access the problem database,
> and 57 of 60 are non-idle.
> We only need to gdb those 57 processes, or
> we need gdb 60 or 170?
Potentially the deadlock could be anywhere :-(. You should definitely
not assume it must be one of the processes connected to the problem
database, because the buffer pool is cluster-wide.
Might be worth setting up a shell script to help.
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: <13105.1088623982@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