Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid` - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid`
Date
Msg-id 20160307162123.GA841947@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid`  (Brian Ghidinelli <brian@vfive.com>)
Responses Re: BUG #13970: Vacuum hangs on particular table; cannot be terminated - requires `kill -QUIT pid`
List pgsql-bugs
Brian Ghidinelli wrote:
> Any chance that a DDL modification like adding a column would effect an update of those values across the table?

If a column is added without a default value, then the existing tuples
are not touched.  If a default value is added, then the complete table
is rewritten.  I suppose that the rewritten table would not include old
Multixact values in XMAX, but I haven't checked.

I wonder if it's possible for a column to be added in an operation that
does not rewrite the table yet the relminmxid is advanced past the
oldest multixact present.

I assume, given the lack of traffic in this thread, that you have solved
your problem already?

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-bugs by date:

Previous
From: armin.schoeffmann@aegaeon.de
Date:
Subject: BUG #14004: pg_restore never returns on premature EOF of input file if invoked with with parallel job option
Next
From: Michael Paquier
Date:
Subject: Re: BUG #14001: pg_ctl error output empty/faulty