Message-ID: <58D3BEBF.9020701@sqlexec.com>
Date: Thu, 23 Mar 2017 08:25:35 -0400
From: "michael@sqlexec.com" <michael@sqlexec.com>
User-Agent: Postbox 5.0.11 (Windows/20170302)
MIME-Version: 1.0
To: ramonpadilla1@yahoo.co.uk
CC: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: pg_dump ERROR: missing chunk number 0 for toast value
References: <587579712.444477.1490174496291.ref@mail.yahoo.com>
 <587579712.444477.1490174496291@mail.yahoo.com>
In-Reply-To: <587579712.444477.1490174496291@mail.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

As a start, zero in on the relation, index,column, table:

select 36791::regclass;


Restart the server with:

zero_damaged_pages=true
ignore_system_indexes=true


Do full vacuum again:
VACUUM FULL VERBOSE public.bodycontent;

If still a problem, consider dropping all the indexes and recreate 
them.  Then try to do the vacuum full again.

If you still have a problem:
Use a program like python/psycopg2 and write a loop that fetches every 
row in the table and capture with exception the rows that it fails on. 
Then delete those rows.  Then do a dump of the table to /dev/null and 
see if it completes without errors. If so, you will need to dump and 
recreate the table.

Regards,
Michael Vitale


ramonpadilla1@yahoo.co.uk wrote:
> missing chunk


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin