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

Any chance that a DDL modification like adding a column would effect an upda=
te of those values across the table?

Brian=20

> On Feb 19, 2016, at 13:45, Alvaro Herrera <alvherre@2ndquadrant.com> wrote=
:
>=20
> Here's another idea: just try SELECT FOR UPDATE on the offending tuple.
> As I recall, that code path has enough protections that we wouldn't try
> to read the members of the multixact even if we don't see it as below
> the horizon, simply by checking the infomask bits as I mentioned before.
>=20
> You could try SELECT FOR UPDATE the complete table.  If you had debug
> symbols you could grab the specific TID that's giving you trouble from
> the backtrace ... but then the table is not *that* large.
>=20
> --=20
> =C3=81lvaro Herrera                http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>=20
>=20
> --=20
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs