Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
| От | Tom Lane |
|---|---|
| Тема | Re: ANALYZE locks pg_listener in EXCLUSIVE for long time? |
| Дата | |
| Msg-id | 3810.1083552321@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | ANALYZE locks pg_listener in EXCLUSIVE for long time? (Philip Warner <pjw@rhyme.com.au>) |
| Ответы |
Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Re: ANALYZE locks pg_listener in EXCLUSIVE for long |
| Список | pgsql-hackers |
Philip Warner <pjw@rhyme.com.au> writes:
> Does this mean that ANALYZE will take an exclusive lock on pg_listener
> until the ANALYZE finishes? Or is there some other cause?
ANALYZE does not take an exclusive lock on anything. However, the
async.c functions want AccessExclusiveLock on pg_listener, so they
quite possibly would get blocked by ANALYZE's not-so-exclusive lock.
Possibly we could reduce the strength of the lock taken by the async.c
functions ... I haven't thought hard about it. The long-term answer is
certainly a wholesale rewrite of the listen/notify mechanism.
regards, tom lane
В списке pgsql-hackers по дате отправления: