Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Date: 2004-05-03 15:15:08
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184D0B2@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> * Is it really a good idea for database-wide ANALYZE to run as a single
> transaction? Holding all those locks is a recipe for deadlocks, even
> if they're as inoffensive as AccessShareLocks normally are.

Wasn't one idea behind that change also to not make the planner create a plan
from mixed old and new statistics ? I guess that could later be accomplished with
"begin work; analyze; commit work;" (with subtransactions) though.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-05-03 15:19:57 Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Previous Message Andrew Hammond 2004-05-03 15:08:03 Re: Is there any method to keep table in memory at startup