From: | Dinesh Bhandary <dbhandary(at)iii(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | concurrent delete in postgers/error pg_restore |
Date: | 2010-10-08 23:34:02 |
Message-ID: | 4CAFAA6A.2050302@iii.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
HI All,
I feel like I am in a very weird situation. I took a postgres dump
because db was bloated and in the process of restoring it and running
into several issues.
I run postgres 8.4.1 on red hat.
Here is what id did.
1) pg_dump
2) drop db
3) pg_restore on the same cluster ( where there are more than one
instance of databases running) where it creates a db.
restore is complaining about a single table which happens to be large (
aboutt 30 million rows). Restore process can't seem to add foreign key
constraints and fails with the following error:
could not access status of transaction ... . pg_clog file does not
exist. Why does it care about pg_clog file when it is just a restore
from a good dump.
When I tried to add a constraint separately, it says - "concurrent
delete in progress".
I am at loss on why I keep on getting these weird error messages. It is
supposed to be simple dump/restore process.
Any ideas??
I appreciate your help. Thanks.
Dinesh
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Burgholzer | 2010-10-10 11:21:12 | Vaccuuming every db in cluster fails to eliminate "execute a full-database VACUUM in..." |
Previous Message | Marcelo Leite | 2010-10-08 19:33:23 | Prepared Transactions |