Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-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


pgsql-hackers by date

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

pgsql-admin by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group