From: David F. Skoll <dfs@roaringpenguin.com>
To: pgsql-admin@postgresql.org
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Subject: Re: A real puzzler: ANY way to recover?
Date: Thu, 05 May 2005 14:06:33 -0400
Message-ID: <427A60A9.7080309@roaringpenguin.com> (raw)
In-Reply-To: <20050505174936.GA19346@dcc.uchile.cl>
References: <427A5472.8060004@roaringpenguin.com>
<20050505174936.GA19346@dcc.uchile.cl>
Alvaro Herrera wrote:
> Connect in standalone mode?
Does not work. Tom Lane replied with the only thing that does work,
which we independently discovered about 30 seconds before hearing from
Tom. :-)
The solution is to modify the PostgreSQL source code to skip the check,
and run the modified binary in standalone mode just to reset the
datallowconn flag to true. Once we did that, we quit and started
the normal server to complete the maintenance work.
I recommend having a postgres single-user-mode command-line option
to disable the check, with a suitably stern warning in the man
page not to use it. :-)
Regards,
David.
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: dfs@roaringpenguin.com, alvherre@dcc.uchile.cl
Subject: Re: A real puzzler: ANY way to recover?
In-Reply-To: <427A60A9.7080309@roaringpenguin.com>
* 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