Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock
Date: 2009-08-07 19:58:48
Message-ID: 20090807195848.GC5290@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-08-07 20:00:26 Re: Alpha releases: How to tag
Previous Message Bruce Momjian 2009-08-07 19:58:25 Re: Alpha releases: How to tag