Horton
Menu

Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Cédric Villemain <cedric.villemain.debian@gmail.com>, Peter Eisentraut <peter_e@gmx.net>, Simon Riggs <simon@2ndquadrant.com>, Alvaro Herrera <alvherre@commandprompt.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2010-07-10T20:17:05Z
Lists: pgsql-hackers 
Robert Haas wrote:
> On Wed, Jul 7, 2010 at 9:04 PM, C?dric Villemain
> <cedric.villemain.debian@gmail.com> wrote:
> >>> > I assume this did not get done for 9.0. ?Do we want a TODO item?
> >>>
> >>> Yes.
> >>
> >> Added:
> >>
> >> ? ? ? ?Reduce locking required for ALTER commands
> >
> > I just faced production issue where it is impossible to alter table to
> > adjust autovacuum settings in a pg8.4. (5K tps, 260M rows table, lock
> > too much)
> >
> > Can we add some mechanism to prevent that situation also in the TODO item ?
> >
> > (alternative is actualy to alter other tables and adjust the
> > postgresql.conf for biggest tables, but not an ideal solution anyway)
> >
> >>
> >> ? ? ? ? ? ?* http://archives.postgresql.org/pgsql-hackers/2009-08/msg00533.php
> >> ? ? ? ? ? ?* http://archives.postgresql.org/pgsql-hackers/2009-10/msg01083.php
> >> ? ? ? ? ? ?* http://archives.postgresql.org/pgsql-hackers/2010-01/msg02349.php
> 
> Bruce, that last link is about something else completely.  Here are
> some better ones:
> 
> http://archives.postgresql.org/pgsql-hackers/2008-10/msg01248.php
> http://archives.postgresql.org/pgsql-hackers/2008-10/msg00242.php

Thanks, TODO updated.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + None of us is going to be here forever. +