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

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

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: rm_cleanup functions need to be allowed towrite WAL entries.
Date: 2009-08-09 21:22:32
Message-ID: 1249852952.4839.496.camel@ebony.2ndQuadrant (view raw or flat)
Thread:
Lists: pgsql-committers
On Sun, 2009-08-09 at 11:41 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > I want to move in the direction of having two cleanup routines, one
> > executed before recovery ends and one done afterwards, so it can write
> > WAL. Perhaps these would be called rm_makesafe() and rm_repair(). Rough
> > thinking at this stage.
> 
> > The rm_repair() would execute in a separate process once we're up.
> 
> 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.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

Responses

pgsql-committers by date

Next:From: Tom LaneDate: 2009-08-09 21:26:49
Subject: Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
Previous:From: User BmomjianDate: 2009-08-09 16:30:10
Subject: pg-migrator - pg_migrator: Clarify which restrictions are 8.3 -> 8.4

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