Re: A real puzzler: ANY way to recover? - Mailing list pgsql-admin

From Rosser Schwarz
Subject Re: A real puzzler: ANY way to recover?
Date
Msg-id 37d451f705050510373e9a34ab@mail.gmail.com
Whole thread Raw
In response to A real puzzler: ANY way to recover?  ("David F. Skoll" <dfs@roaringpenguin.com>)
Responses Re: A real puzzler: ANY way to recover?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
while you weren't looking, David F. Skoll wrote:

> Is there any way to recover short of nuking everything and
> restoring from a backup dump? :-(

I don't have any ability to test this and see if it actually works,
but a priori, I'd suggest trying, as your postgres user:

$ createdb oopswow
$ psql oopswow
oopswow=# update pg_database set datallowconn = true; -- with optional
WHERE clause
oopswow=# \q

That should work.  Unless the new database takes its datallowconn
attribute from the template database, which will have been set to
false by the errant UPDATE -- in which case, I've no idea.

/rls

--
:wq

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: A real puzzler: ANY way to recover?
Next
From: Alvaro Herrera
Date:
Subject: Re: A real puzzler: ANY way to recover?