Re: dumping tables from badly damaged db

From: Brian Ristuccia <bristucc(at)sw(dot)starentnetworks(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: dumping tables from badly damaged db
Date: 2003-10-31 19:15:46
Message-ID: 20031031191546.GC24232@sw.starentnetworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Fri, Oct 31, 2003 at 02:05:57PM -0500, Tom Lane wrote:
>
> You might be able to get past this by starting a standalone postgres
> with the -P command-line option (ignore system indexes). If so, try
> "select relname, relfilenode from pg_class". With luck that will give
> you a list of which file name is needed for each table. I'd not counsel
> trying to do more than that in the standalone backend until you've
> gotten at least the tables put back together.
>

The standalone backend errors out with:

FATAL 1: _mdfd_getrelnfd: cannot open relation pg_trigger: No such file or
directory

I suspect my troubles may be more severe than just a missing index... My
week-old backups are starting to look more and more attractive.

Any other hints?

Thanks.

-Brian

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message PostgreSQL 2003-10-31 19:33:09 SELECT COUNT(*)... returns 0 ROWS
Previous Message Tom Lane 2003-10-31 19:05:57 Re: dumping tables from badly damaged db