We have a database (PostgreSQL 9.3.10) which is reporting this error on a TOAST table on a VACUUM. Is there a
canonicalway of repairing this? The table is *huge*, so a VACUUM FULL or pg_dump / pg_restore is probably not going to
work.
--
-- Christophe Pettus
xof@thebuild.com