Re: how to use pg_resetxlog - closer ...

From: "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com>
To: "'''pgsql-general(at)postgresql(dot)org ' ' '" <pgsql-general(at)postgresql(dot)org>
Subject: Re: how to use pg_resetxlog - closer ...
Date: 2003-10-22 14:11:13
Message-ID: 73309C2FDD95D11192E60008C7B1D5BB05FEDAEC@snt452.corp.bcbsm.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks to all ... I think I'm closer to at leasting
something useful as far as the database is concern.

Recap: Running PostgreSQL 7.2.1 on RedHat Linux 7.2
and I just experienced a RAID failure with the DB
still active. Tom pointed me in the area of the file
'1249' which was no longer in my database directory.
I copied that from anther directory and got part
of the way there. There were some errors regarding
missing files in pg_clog - I faked that, too.

Now: I am getting an error when I try to do a select
from any table :

[snip]
cannot find attribute 1 of relation <table>
[/snip]

Looking in the groups.google.com, I see similar things
which was fixed with running PostgreSQL in stand alone
mode and forcing a reindex. When I tried that, I got:

[snip error]

[/snip]
backend> reindex database testdb force ;
DEBUG: StartTransactionCommand
DEBUG: query: reindex database testdb force ;

DEBUG: ProcessUtility: reindex database testdb force ;

ERROR: Cannot create unique index. Table contains non-unique values
DEBUG: AbortCurrentTransaction
[snip error]

Is there a way around this so I can at least dump some
data?

Thanks bunches!

-X

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stan Leung 2003-10-22 14:30:24 Clustering for performance and fail over
Previous Message Tom Lane 2003-10-22 13:58:56 Re: unexpected query behavior with UTF text