From: Rosser Schwarz <rosser.schwarz@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: A real puzzler: ANY way to recover?
Date: Thu, 5 May 2005 12:37:42 -0500
Message-ID: <37d451f705050510373e9a34ab@mail.gmail.com> (raw)
In-Reply-To: <427A5472.8060004@roaringpenguin.com>
References: <427A5472.8060004@roaringpenguin.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rosser.schwarz@gmail.com
Subject: Re: A real puzzler: ANY way to recover?
In-Reply-To: <37d451f705050510373e9a34ab@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox