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

From Bruce Momjian
Subject Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Date
Msg-id 200405030313.i433D4M13962@candle.pha.pa.us
Whole thread Raw
In response to Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
List pgsql-hackers
Tom Lane wrote:
> 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.

Gavin was working on it a while ago but I am not sure how far he got.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Claudio Natoli
Date:
Subject: Re: Fixed directory locations in installs
Next
From: Philip Warner
Date:
Subject: Re: ANALYZE locks pg_listener in EXCLUSIVE for long