Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries. - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
Date
Msg-id 200908101909.n7AJ9Km26419@momjian.us
Whole thread Raw
In response to Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
List pgsql-committers
Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > On Sun, 2009-08-09 at 11:41 -0400, Tom Lane wrote:
> >> Er, what's the point of that?
>
> > Rebuilding damaged indexes automatically, rather than barfing. I regard
> > that as a long term extension of crash recovery to bring a database back
> > to a usable state.
>
> Having crash recovery auto-rebuild indexes it thinks are damaged seems
> to me to be a pretty horrid idea.  Just for starters, it would overwrite
> forensic evidence about the cause of the damage.  A DBA might not wish
> the rebuild to happen *right then* in any case.

Are hash indexes going to need auto-rebuild, or can we make them
WAL-safe eventually?

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Support EEEE (scientific notation) in to_char().
Next
From: Tom Lane
Date:
Subject: Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.