From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sribeiro <info@simetriastudio.com>
cc: pgsql-sql@postgresql.org
Subject: Re: Re: ERROR while creating new user - could not open relation
 mapping file global/pg_filenode.map
In-reply-to: <1448386072130-5874934.post@n5.nabble.com>
References: <1448307482990-5874842.post@n5.nabble.com>
 <565378B4.5080801@aklaver.com> <1448311158958-5874860.post@n5.nabble.com>
 <1448386072130-5874934.post@n5.nabble.com>
Comments: In-reply-to Sribeiro <info@simetriastudio.com>
 message dated "Tue, 24 Nov 2015 10:27:52 -0700"
Date: Tue, 24 Nov 2015 17:02:43 -0500
Message-ID: <32161.1448402563@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Sribeiro <info@simetriastudio.com> writes:
> Anyone has any idea what i need to do fix this issue?

You don't have an up-to-date backup, eh?

You might be able to fix this by doing a fresh initdb (targeting some
other location for the data directory, of course, but being careful
to use the exact same Postgres version) and then copying the
global/pg_filenode.map file out of that data directory and into your
broken one.  This would only work if you've never done a VACUUM FULL on
any of the shared catalogs in the existing data directory, so it's far
from guaranteed to work; but it's worth a try.

BTW, before any sort of manual data-directory surgery like this, it
would be a wise idea to make a backup copy of the entire data directory
file tree, e.g. with tar.  That way you can at least get back to where
you were if you break it worse.  Though I'm afraid you might end up
having to write off this installation as a learning experience :-(

			regards, tom lane


-- 
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql