From: Tom Lane <tgl@sss.pgh.pa.us>
To: David F. Skoll <dfs@roaringpenguin.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: A real puzzler: ANY way to recover?
Date: Thu, 05 May 2005 13:34:29 -0400
Message-ID: <25148.1115314469@sss.pgh.pa.us> (raw)
In-Reply-To: <427A5472.8060004@roaringpenguin.com>
References: <427A5472.8060004@roaringpenguin.com>
"David F. Skoll" <dfs@roaringpenguin.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
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: tgl@sss.pgh.pa.us, dfs@roaringpenguin.com
Subject: Re: A real puzzler: ANY way to recover?
In-Reply-To: <25148.1115314469@sss.pgh.pa.us>
* 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