Tom Lane wrote:
Alvaro Herrera <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
