Christophe Pettus wrote: > We have a database (PostgreSQL 9.3.10) which is reporting this error on a > TOAST table on a VACUUM. Is there a canonical way of repairing this? The > table is *huge*, so a VACUUM FULL or pg_dump / pg_restore is probably not > going to work.
I don't think toast tables can have multixacts at all, so my guess is that the tuple header is corrupted. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
