sanity check error for pg_dump

From: PRAGATI SAVAIKAR <pragati(at)phil(dot)com(dot)sg>
To: pgsql-bugs(at)postgresql(dot)org
Subject: sanity check error for pg_dump
Date: 2001-04-04 04:40:40
Message-ID: 3ACAA5C8.D2E46336@phil.com.sg
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Currently we have upgraded postgres from 7.0.2 to postgres7.0.3
version on Linux 2.2.16-22smp #1 SMP 2000 i686 unknown .
And we take backup of our postgres database on daily bases through
cron using following scripts

*****
# Script to backup the minx databases

daymon="`date +%d``date +%b`"
BACKPATH='/usr/local/pgsql/minx/backup'

# Create dump of 250 and 300 databases

pg_dump minx250 -f $BACKPATH/$daymon-250-dump.ti
pg_dump minx300 -f $BACKPATH/$daymon-300-dump.ti

# Compress the backups

compress $BACKPATH/$daymon-250-dump.ti
compress $BACKPATH/$daymon-300-dump.ti

***** End Of Script ***********

The total size of our database is 3.8G . and available disk space
is 4.8 G
We have recently started getting following error messages

failed sanity check, table arind was not found
failed sanity check, table inpart was not found

due to which pg_dump process does not get complete.

We have tried droping and recreating the table which has caused
error . but it didn't help . Vacuum goes through for those tables.

Please tell us what has to be done in such instance .

Regards,
Pragati

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Philip Warner 2001-04-04 06:49:47 Re: Table constraint ordering disrupted by pg_dump
Previous Message Tom Lane 2001-04-04 04:31:27 Re: Table constraint ordering disrupted by pg_dump