From: | <ramonpadilla1(at)yahoo(dot)co(dot)uk> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | pg_dump ERROR: missing chunk number 0 for toast value |
Date: | 2017-03-22 09:21:36 |
Message-ID: | 587579712.444477.1490174496291@mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I'm using PostgreSQL 9.3.16 on Windows 7 and the data directory was created from a filesystem backup of an installation running on another machine, which failed.
After starting the postgres service I ran `pg_dump` using pgAdminIII to backup the databases.
pg_dump.exe --host localhost --port 5433 --username "postgres" --no-password --format custom --blobs --verbose --file "db-2017-03-22.backup" "mydb"
One of them reported the following error:
pg_dump: dumping contents of table "public.bandana"
pg_dump: dumping contents of table "public.bodycontent"
pg_dump: Dumping the contents of table "bodycontent" failed: PQgetResult() failed.
pg_dump: Error message from server: ERROR: missing chunk number 0 for toast value 314936 in pg_toast_36791
pg_dump: The command was: COPY public.bodycontent (bodycontentid, body, contentid, bodytypeid) TO stdout;
Process returned exit code 1.
Since then I've done some digging around and run the following commands:
REINDEX table pg_toast.pg_toast_36791;
VACUUM ANALYZE bodycontent;
Both return:
Query returned successfully with no result in xx ms.
Using pgAdmin I've selected the Maintenace option and run a VACUUM (no options) , ANALYSE and REINDEX and no errors were reported.
I ran VACUUM with the FULL option and the following error was reported:
INFO: vacuuming "public.plugindata"
ERROR: missing chunk number 0 for toast value 289849 in pg_toast_36998
I don't have any experience with postgres or databases in general. Can anyone advise what I should do next?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-03-22 13:15:49 | Re: |
Previous Message | Santiago DIEZ | 2017-03-22 08:53:26 | Re: |