From: Tom Lane <tgl@sss.pgh.pa.us>
To: David F. Skoll <dfs@roaringpenguin.com>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: A real puzzler: ANY way to recover?
Date: Thu, 05 May 2005 14:19:15 -0400
Message-ID: <25542.1115317155@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? :-(
BTW, am I right in guessing that you got into this fix by sloppy
application of the directions for fixing template0 for the recent
security issues?
Although I dislike last-minute fixes, I am strongly tempted to put in
the ignore-datallowconn-if-standalone change in all the releases we are
about to make. It'd be a one-liner that is very unlikely to break
anything, and I have this nasty feeling that you may not be the only
guys to make this mistake.
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, pgsql-hackers@postgresql.org
Subject: Re: A real puzzler: ANY way to recover?
In-Reply-To: <25542.1115317155@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