We had recently taken an online backup of our production database cluster (pg_start_backup() - rsync - pg_stop_backup()).
We had built the testing cluster with the backup.
When we try to vacuum the database or vacuum full the testing database, we are getting the following error.
vacuuming of database.... failed: ERROR: could not open file "base/44620/972355": No such file or directory
In an other situation-
postgres=# select * from table1 limit 10;
ERROR: could not open file "base/44620/1022275": No such file or directory
After going through the below thread, one situation which we believe could be the problem is -
- Table1 is a partitioned table and we keep dropping and adding partitions on daily basis. This might have happened at the time we were backing up.
Is this the problem ? If yes, what precautions we need to take ? perform the backup when there are no DDLs are happening ?
Both the base files "972355" and "1022275" are not existing in production (probably they belong to dropped partitions -- not sure).
We have a data center migration coming up, so, this is very critical for us -
PG Version - 9.0.1
OS - RHEL 5.5 (prod) and RHEL 6.1 (test)
Please help
Thanks
VB
