X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D061C53DC0 for ; Thu, 5 May 2005 14:37:44 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 07899-10 for ; Thu, 5 May 2005 17:37:43 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by svr1.postgresql.org (Postfix) with ESMTP id 13CD553DAE for ; Thu, 5 May 2005 14:37:42 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so818766wri for ; Thu, 05 May 2005 10:37:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=i39LQNNAw39dZZ8EArCWsf7Q5VP2ohe/fOskgOJUMduynzjwroZtL/sqqiAKWiopMH0J5BmXK3nSMMudniX11NNlKflxQlJ3uB19zVucc0+ZGaeubXRM3O0KZY7mLIjaLi9U0GL+fdj6cYRPs5xH7bRRqT1+J6lWNGmhHBHONwU= Received: by 10.54.73.2 with SMTP id v2mr317040wra; Thu, 05 May 2005 10:37:42 -0700 (PDT) Received: by 10.54.99.14 with HTTP; Thu, 5 May 2005 10:37:42 -0700 (PDT) Message-ID: <37d451f705050510373e9a34ab@mail.gmail.com> Date: Thu, 5 May 2005 12:37:42 -0500 From: Rosser Schwarz Reply-To: Rosser Schwarz To: pgsql-admin@postgresql.org Subject: Re: A real puzzler: ANY way to recover? In-Reply-To: <427A5472.8060004@roaringpenguin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <427A5472.8060004@roaringpenguin.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.275 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200505/51 X-Sequence-Number: 17480 while you weren't looking, David F. Skoll wrote: > Is there any way to recover short of nuking everything and > restoring from a backup dump? :-( I don't have any ability to test this and see if it actually works, but a priori, I'd suggest trying, as your postgres user: $ createdb oopswow $ psql oopswow oopswow=3D# update pg_database set datallowconn =3D true; -- with optional WHERE clause oopswow=3D# \q That should work. Unless the new database takes its datallowconn attribute from the template database, which will have been set to false by the errant UPDATE -- in which case, I've no idea. /rls -- :wq