From: | Leif Biberg Kristensen <leif(at)solumslekt(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: I/O error on data file, can't run backup |
Date: | 2011-10-05 18:48:05 |
Message-ID: | 201110052048.05829.leif@solumslekt.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday 5. October 2011 20.42.00 Tom Lane wrote:
> Postgres can't magically resurrect data that your drive lost, if that's
> what you were hoping for. However, you might be in luck, because that
> file is probably just an index and not original data. Try this:
>
> select relname from pg_class where relfilenode = 11658;
>
> On my 9.0 installation I get "pg_opclass_am_name_nsp_index". If you get
> the same (or any other index for that matter) just reindex that index
> and you'll be all right ... or at least, you will be if that's the only
> file your drive has lost.
Tom,
this is what I get:
postgres(at)balapapa ~ $ psql pgslekt
psql (9.0.5)
Type "help" for help.
pgslekt=# select relname from pg_class where relfilenode = 11658;
relname
-------------
pg_opfamily
(1 row)
regards, Leif
From | Date | Subject | |
---|---|---|---|
Next Message | Leif Biberg Kristensen | 2011-10-05 19:06:16 | Re: I/O error on data file, can't run backup |
Previous Message | Tom Lane | 2011-10-05 18:42:00 | Re: I/O error on data file, can't run backup |