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.
-- -- Christophe Pettus [email protected] -- Sent via pgsql-general mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
