| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Meaning of transaction pg_locks? |
| Date: | 2008-11-12 02:38:30 |
| Message-ID: | 491A41A6.3050202@rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Can anyone explain the way to debug this kind of situation and/or
explain the meaning of these locks?
Partial output of "select * from pg_locks":
| | 1192675195 | 62860 | ShareLock | f
| | 1192675195 | 62814 | ExclusiveLock | t
| | 1192675195 | 62838 | ShareLock | f
| | 1192675195 | 63525 | ShareLock | f
where 1192675195 is the 'transaction' field.
I am not at all clear what the processes are waiting for, or if there is
a way to reduce such contention.
--
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 03 5330 3171 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
http://www.rhyme.com.au <http://www.rhyme.com.au/>
| / \|
| --________--
GPG key available upon request. | /
|/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2008-11-12 02:51:12 | Re: Meaning of transaction pg_locks? |
| Previous Message | Tom Lane | 2008-11-12 02:37:00 | Re: Optimizing COPY |