Re: BUG #2285: Can not access database after successful PITR - file naming problems - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #2285: Can not access database after successful PITR - file naming problems
Date
Msg-id 20484.1141061636@sss.pgh.pa.us
Whole thread Raw
In response to BUG #2285: Can not access database after successful PITR - file naming problems  ("Nicholas Vinen" <hb@pg.x256.org>)
List pgsql-bugs
"Nicholas Vinen" <hb@x256.com> writes:
> Now, when I try to use PITR to restore the database on my test server, the
> PITR succeeds as normal, but I can not access the database with an error
> like:

> psql: FATAL:  could not open relation 1663/16385/605464: No such file or
> directory

This seems pretty ugly :-(.  Unless you've got some odd stuff in
~/.psqlrc, I would think that psql startup could only cause accesses to
system catalogs, but 605464 is far beyond the normal relfilenode numbers
assigned to any system catalogs or indexes.  AFAICS the only way that a
new relfilenode would be assigned is during TRUNCATE, CLUSTER or
REINDEX ... have you done any of those on system catalogs?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2286: Wrong index creation with cs_CZ locales and HYPHEN
Next
From: Frank van Vugt
Date:
Subject: has_table/schema_privilige() returns incorrect info on temp tables