Skip site navigation (1) Skip section navigation (2)

Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
Date: 2009-10-19 15:56:29
Message-ID: 20091019155629.GB3352@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Simon Riggs wrote:
> 
> On Fri, 2009-08-07 at 15:58 -0400, Alvaro Herrera wrote:
> > Tom Lane wrote:
> > > Peter Eisentraut <peter_e(at)gmx(dot)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.
> 
> I was intending to finish that patch in this release cycle.

Since you're busy with Hot Standby, any chance you could pass it on?


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

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2009-10-19 16:00:37
Subject: Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
Previous:From: Kevin GrittnerDate: 2009-10-19 15:53:41
Subject: Re: Application name patch - v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group