ANALYZE locks pg_listener in EXCLUSIVE for long time?
От | Philip Warner |
---|---|
Тема | ANALYZE locks pg_listener in EXCLUSIVE for long time? |
Дата | |
Msg-id | 6.1.0.6.0.20040503112948.04e2d280@203.8.195.10 обсуждение исходный текст |
Ответы |
Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
|
Список | pgsql-hackers |
We are seeing occasional long lockouts from out DB. When I do a 'select * from pg_locks', I find that everybody is waiting for pg_listener, and that the lock on pg_listener is currently held by a long-running ANALYZE VERBOSE. I saw the following in the change logs (not sure if it's relevant): should have gotten this notify. But to do that, we'd have to wait to see if he commits or not, or make UNLISTENhold exclusive lock on pg_listener until commit. Either of these answers is deadlock-prone, not tomention horrible for interactive performance. Do it this way for now. (What happened to that project todo LISTEN/NOTIFY in memory with no table, anyway?) Does this mean that ANALYZE will take an exclusive lock on pg_listener until the ANALYZE finishes? Or is there some other cause? Any help or suggestions would be appreciated... ---------------------------------------------------------------- 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 |/
В списке pgsql-hackers по дате отправления: