pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Si Chen <schen@graciousstyle.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@postgresql.org
Subject: Re: [ADMIN] how to find transaction associated with a lock
Date: Thu, 22 Jul 2004 14:44:29 -0700
Message-ID: <4100353D.9080202@graciousstyle.com> (raw)
In-Reply-To: <12341.1090529103@sss.pgh.pa.us>
References: <41001296.3090609@graciousstyle.com>
	<12341.1090529103@sss.pgh.pa.us>

Hi Tom,

Thanks for the reply.  I looked in pg_stat_activity and it shows 
database tables and process ids.  So I should be using the pid next to 
the ExclusiveLock to see what database it is working on, right?

Now, the problem that I had was this: I have a java application that 
access postgresql (7.3.2) via jdbc.  It was running fine for a while, 
then of all sudden, against one table, the INSERT would simply hang.  It 
would INSERT fine on many other tables and the application could still 
run, except for INSERTs involving this particular table (unfortunately, 
an important table.)

Someone else had suggested that it was perhaps a lock on that particular 
table.  So I looked up view locking and then thought that this was where 
the bug was occurring.  Do you think I'm looking down the wrong path?  
Might it be something else (like the lack of a recent vacuuming or fsync 
not being set to true in postgresql.conf) that was causing this bug?

Thanks so much for your help!

Si Chen

Tom Lane wrote:

>Si Chen <schen@graciousstyle.com> writes:
>  
>
>>Does anyone know of a way to go from transactions identifiers to the 
>>actual transaction--which tables, which statements, etc. etc.?
>>    
>>
>
>See pg_stat_activity.
>
>The pg_locks entries you are looking at do *not* represent table locks
>of any kind.  This:
>  
>
>>NULL NULL 3366868 27149 ExclusiveLock TRUE
>>    
>>
>simply says that transaction 3366868 is still running.  This:
>  
>
>>NULL NULL 3366868 1069 ShareLock FALSE
>>    
>>
>says that process 1069 has elected to wait until transaction 3366868
>finishes.  Normally the reason for doing that would be that transaction
>3366868 holds a row lock (SELECT FOR UPDATE lock) on some row that
>process 1069's transaction wants to acquire row lock on.
>
>However, I suspect what you are really wishing is to find out the
>individual row that is being contended for, and there is not enough
>information in the system views to do that (mainly because we do not
>keep per-row locking information in shared memory).
>
>			regards, tom lane
>
>  
>




view thread (6+ messages)  latest in thread

Message-ID: <4100353D.9080202@graciousstyle.com>
Permalink:  ../4100353D.9080202@graciousstyle.com/
Also on:    postgresql.org/message-id/4100353D.9080202@graciousstyle.com

 · 

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 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: schen@graciousstyle.com, tgl@sss.pgh.pa.us, pgsql-general@postgresql.org
  Subject: Re: [ADMIN] how to find transaction associated with a lock
  In-Reply-To: <4100353D.9080202@graciousstyle.com>
  References: <41001296.3090609@graciousstyle.com> <12341.1090529103@sss.pgh.pa.us> <4100353D.9080202@graciousstyle.com>

* 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