Hi Naveen,
Normally we see the chunk errors comes due to the disk IO storage level issues and it leads towards the data corruption.
Normally we see the chunk errors comes due to the disk IO storage level issues and it leads towards the data corruption.
Try reindexing or vacuuming otherwise it may need a detailed analysis to resolve these chunk errors.
On Wed, Jul 18, 2018 at 9:15 PM, Naveen Kumar <naveenchowdaryon@xxxxxxxxx> wrote:
Hello Experts,What could be the reason for bellow errors. Can one help me to fix this?PostgreSQL Database: [~rptdb~] Data Backup Failed with PostgreSQL Error: [~pg_dump: Dumping the contents of table "document" failed: PQgetResult() failed.pg_dump: Error message from server: ERROR: unexpected chunk number 452 (expected 0) for toast value 94674063 in pg_toast_56980977pg_dump: The command was: COPY reports_extended.document (document_id, access_key, created_date, document_name, document_size, document_status, document_type, encryption_type, external_system_storage_id, external_system_storage_url, last_updated_date, md5_hash, source_system_name, storage_type, created_by, customer_org_id, content_type, tags, file, ownedby) TO stdout;~].Thanks & Regards,
Naveen Kumar .M,
Sr. PostgreSQL Database Administrator,
Mobile: 7755929449.
My attitude will always be based on how you treat me.
