Skip site navigation (1) Skip section navigation (2)

Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
Date: 2009-08-09 21:26:49
Message-ID: 26576.1249853209@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Simon Riggs <simon(at)2ndQuadrant(dot)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.

			regards, tom lane

In response to

Responses

pgsql-committers by date

Next:From: Peter EisentrautDate: 2009-08-09 22:47:59
Subject: pgsql: Ship documentation without intermediate tarballs Documentation
Previous:From: Simon RiggsDate: 2009-08-09 21:22:32
Subject: Re: pgsql: rm_cleanup functions need to be allowed towrite WAL entries.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group