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

From Philip Warner
Subject Re: ANALYZE locks pg_listener in EXCLUSIVE for long
Date
Msg-id 6.1.0.6.0.20040504013635.049fda38@203.8.195.10
Whole thread Raw
In response to Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 01:30 AM 4/05/2004, Tom Lane wrote:
>can only occur if other
>transactions running parallel to the ANALYZE perform sufficient catalog
>updating activity to fill the sinval message queue.  And there must also
>be at least one long-term-idle backend, so that the queue doesn't get
>drained.

Sounds quite likely; usually seems to occur at 'shoulder' load times; lots 
of updates still happening (several each second) and a server process pool 
that is larger than necessary to handle the load.

I'll replace all:
    heap_openr(ListenerRelationName, AccessExclusiveLock);

with
    heap_openr(ListenerRelationName, ExclusiveLock);

and see how it goes.

Thanks for the help.



----------------------------------------------------------------
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 by date:

Previous
From: Paul Ramsey
Date:
Subject: Re: PostgreSQL pre-fork speedup
Next
From: Alvaro Herrera
Date:
Subject: Re: Weird prepared stmt behavior