Re: ANALYZE locks pg_listener in EXCLUSIVE for long time? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Date
Msg-id 3810.1083552321@sss.pgh.pa.us
Whole thread Raw
In response to ANALYZE locks pg_listener in EXCLUSIVE for long time?  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: ANALYZE locks pg_listener in EXCLUSIVE for long  (Philip Warner <pjw@rhyme.com.au>)
List 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 by date:

Previous
From: Claudio Natoli
Date:
Subject: Re: [pgsql-hackers-win32] Timezone database questions
Next
From: Claudio Natoli
Date:
Subject: Re: Fixed directory locations in installs