Re: Endless recovery

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Endless recovery
Date: 2008-03-05 17:00:57
Message-ID: 200803051700.m25H0vu24693@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Simon Riggs wrote:
> On Mon, 2008-02-11 at 09:29 +0100, Hans-Juergen Schoenig wrote:
> > Last week we have seen a problem with some horribly configured
> > machine.
> > The disk filled up (bad FSM ;) ) and once this happened the sysadmi
> > killed the system (-9).
> > After two days PostgreSQL has still not started up and they tried to
> > restart it again and again making sure that the consistency check was
> > started over an over again (thus causing more and more downtime).
> > From the admi point of view there was no way to find out whether the
> > machine was actually dead or still recovering.
>
> I'm sorry to hear about this problem.
>
> Not sure we need a LOG message to warn people about the possible length
> of recovery time. The chances of a recovery taking that much time seem
> very low for normal Postgres, even with checkpoint parameters set at
> their maximum values.
>
> I note that the configuration section does not mention the likely
> increase in recovery time that will result from setting those parameters
> higher. That needs a patch. ISTM a serious omission that should be
> treated as a bug and backpatched.

Patch attached and applied, and backpatched to 8.3.X.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Attachment Content-Type Size
/rtmp/diff text/x-diff 1.6 KB

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2008-03-05 17:46:26 Re: CopyReadLineText optimization
Previous Message Bruce Momjian 2008-03-05 15:53:38 Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit