| From: | "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Subject: | Re: A real puzzler: ANY way to recover? |
| Date: | 2005-05-05 18:06:33 |
| Message-ID: | 427A60A9.7080309@roaringpenguin.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-05 18:14:44 | Re: A real puzzler: ANY way to recover? |
| Previous Message | Alvaro Herrera | 2005-05-05 17:49:36 | Re: A real puzzler: ANY way to recover? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-05 18:06:41 | Re: [pgsql-advocacy] Increased company involvement |
| Previous Message | Marc G. Fournier | 2005-05-05 17:58:53 | Re: [pgsql-advocacy] Increased company involvement |