| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE locks pg_listener in EXCLUSIVE for long |
| Date: | 2004-05-03 08:21:19 |
| Message-ID: | 6.1.0.6.0.20040503181624.0487fd40@203.8.195.10 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 02:54 PM 3/05/2004, Tom Lane wrote:
>Please dig deeper.
I may have found the problem; all the hung processes show 'async_notify
waiting' in ps, and the ANALYZE eventually dies with 'tuple concurrently
updated'.
The routine 'ProcessIncomingNotify' in async.c does indeed try to lock
pg_listener (even if we're not using NOTIFY/LISTEN). Not sure why the
ANALYZE is locking the relation, though...but it is locked in AccessShareLock.
I can send a log of my investigations if necessary.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 03 5330 3172 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-05-03 08:29:41 | Re: inconsistent owners in newly created databases? |
| Previous Message | Christopher Kings-Lynne | 2004-05-03 08:17:41 | OT: Open source developer survey |