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

From Tom Lane
Subject Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
Date
Msg-id 13172.1249832464@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
List pgsql-committers
Simon Riggs <simon@2ndQuadrant.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?  It would make life tremendously harder
for resource managers, which could no longer rely on tracking their
state locally within the startup process.  And AFAICS there is no
benefit to be had, compared to the existing plan of letting backends
run while the startup process is still active.


            regards, tom lane

pgsql-committers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pgsql: rm_cleanup functions need to be allowed to write WAL entries.
Next
From: bmomjian@pgfoundry.org (User Bmomjian)
Date:
Subject: pg-migrator - pg_migrator: Clarify which restrictions are 8.3 -> 8.4