Horton

Re: First steps with 8.3 and autovacuum launcher

Michael Paesold <mpaesold@gmx.at>

View thread View on postgr.es
From: Michael Paesold <mpaesold@gmx.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, "Matthew T. O'Connor" <matthew@zeut.net>, Simon Riggs <simon@2ndquadrant.com>, Heikki Linnakangas <heikki@enterprisedb.com>, Gregory Stark <stark@enterprisedb.com>, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>, Guillaume Smet <guillaume.smet@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2007-10-02T09:19:54Z
Lists: pgsql-hackers 
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
>> How about getting ShareUpdateExclusiveLock on manual analyze and plain
>> AccessShareLock on autovacuum-induced analyze?
> 
> Wouldn't fix the original problem because those two lock types don't
> conflict; hence might as well keep the behavior simple.

What about a new separate lock type for analyze? Couldn't that really 
solve the issue? I know I'm just hand-waving here ;-)

Best Regards
Michael Paesold