Re: A real puzzler: ANY way to recover?

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, pgsql-hackers(at)postgresql(dot)org
Subject: Re: A real puzzler: ANY way to recover?
Date: 2005-05-05 18:19:15
Message-ID: 25542.1115317155@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? :-(

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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Eisentraut 2005-05-05 19:13:56 Re: [HACKERS] A real puzzler: ANY way to recover?
Previous Message Daniel Browning 2005-05-05 18:17:54 Backup when the database is missing all of the pg_* tables

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2005-05-05 18:25:45 Re: [pgsql-advocacy] Increased company involvement
Previous Message Andrew Dunstan 2005-05-05 18:17:12 Re: [pgsql-advocacy] Increased company involvement