From: Tom Lane <tgl@sss.pgh.pa.us>
To: schen@graciousstyle.com
Cc: pgsql-general@postgresql.org
Subject: Re: [ADMIN] how to find transaction associated with a lock
Date: Mon, 26 Jul 2004 12:42:57 -0400
Message-ID: <28911.1090860177@sss.pgh.pa.us> (raw)
In-Reply-To: <4105336E.4030604@graciousstyle.com>
References: <41001296.3090609@graciousstyle.com>
<12341.1090529103@sss.pgh.pa.us>
<4100353D.9080202@graciousstyle.com>
<13323.1090535841@sss.pgh.pa.us>
<4105336E.4030604@graciousstyle.com>
Si Chen <schen@graciousstyle.com> writes:
> Thanks for your help last week. I had the problem again where things
> got hung up during a transaction, and it was at the order_header table.
> Here is what the pg_locks show. Does it confirm what you are saying,
> which is that multiple transactions have tried to insert into this table?
It's impossible to tell much of anything from a partial view of the
pg_locks table. You didn't show us the "granted" flag, so we can't
tell which rows represent held locks and which represent waited-for
locks; and you didn't show transaction locks at all, which are probably
where the issue really is anyway.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, schen@graciousstyle.com, pgsql-general@postgresql.org
Subject: Re: [ADMIN] how to find transaction associated with a lock
In-Reply-To: <28911.1090860177@sss.pgh.pa.us>
References: <41001296.3090609@graciousstyle.com> <12341.1090529103@sss.pgh.pa.us> <4100353D.9080202@graciousstyle.com> <13323.1090535841@sss.pgh.pa.us> <4105336E.4030604@graciousstyle.com> <28911.1090860177@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