| From: | Rosser Schwarz <rosser(dot)schwarz(at)gmail(dot)com> | 
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org | 
| Subject: | Re: A real puzzler: ANY way to recover? | 
| Date: | 2005-05-05 17:37:42 | 
| Message-ID: | 37d451f705050510373e9a34ab@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers | 
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-05-05 17:49:36 | Re: A real puzzler: ANY way to recover? | 
| Previous Message | Tom Lane | 2005-05-05 17:34:29 | Re: A real puzzler: ANY way to recover? | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2005-05-05 17:45:24 | Re: [pgsql-advocacy] Increased company involvement | 
| Previous Message | Tom Lane | 2005-05-05 17:34:29 | Re: A real puzzler: ANY way to recover? |