From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: A real puzzler: ANY way to recover? |
Date: | 2005-05-05 17:34:29 |
Message-ID: | 25148.1115314469@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
"David F. Skoll" <dfs(at)roaringpenguin(dot)com> writes:
> Supposing someone stupidly did this:
> UPDATE pg_database SET datallowconn = false;
> and then closed all the connections to the server.
> Is there any way to recover short of nuking everything and
> restoring from a backup dump? :-(
That would be a bad move.
I wonder whether we should allow a standalone backend (postgres)
to connect regardless of datallowconn. The tradeoff is that you
could break your template0 slightly more easily, but you can break
template0 anyway if you are determined.
If you have actually done that :-(, my recommendation would be to
build a modified backend with the check in
src/backend/utils/init/postinit.c diked out ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rosser Schwarz | 2005-05-05 17:37:42 | Re: A real puzzler: ANY way to recover? |
Previous Message | David F. Skoll | 2005-05-05 17:14:26 | A real puzzler: ANY way to recover? |
From | Date | Subject | |
---|---|---|---|
Next Message | Rosser Schwarz | 2005-05-05 17:37:42 | Re: A real puzzler: ANY way to recover? |
Previous Message | Andreas Pflug | 2005-05-05 17:32:28 | Re: Views, views, views! (long) |