Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
Date
Msg-id 20090807195848.GC5290@alvh.no-ip.org
Whole thread Raw
In response to Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
> > Is there a good reason for $subject, other than that the code is entangled 
> > with other ALTER TABLE code?
> 
> I think it could be lower, but it would take nontrivial restructuring of
> the ALTER TABLE support.  In particular, consider what happens when you
> have a list of subcommands that don't all require the same lock level.
> I think you'd need to scan the list and find the highest required lock
> level before starting ...

IIRC there was a patch from Simon to address this issue, but it had some
holes which he didn't have time to close, so it sank.  Maybe this can be
resurrected and fixed.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Alpha releases: How to tag
Next
From: Bruce Momjian
Date:
Subject: Re: Alpha releases: How to tag