This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---------------------------------------------------------------------------
Simon Riggs wrote:
> On Sun, 2007-06-10 at 20:48 +0200, [EMAIL PROTECTED] wrote:
> > >
> > > > My questions was: why don't we start the archiving *BEFORE* postmaster
> > > > to
> > > > make room.
> > >
> > > The archiver is executed from the postmaster, so thats not possible.
> > >
> > I'm aware of that, my point is maybe the archiver doesn't need postmaster
> > to be fully operational (responding to db requests) to be started
> > > We could investigate where best to put some code, but it wouldn't be
> > > executed very frequently.
> > I agree, OTOH, the more PITR is used on big busy db to more this may
> > happend.
> > >
> > > Why not just execute the archive_command in a script, replacing
> > > the .ready with .done files in archive_status directory when its
> > > processed?
> > >
> > Sure, but if *I* can do it, why can't the system?
> >
> > What do you think,
>
> Just looked at the code. Does seem possible to start archiver earlier -
> it has no hooks into anything else and doesn't need transactions.
>
> Starting archiver earlier would not be the only change required, since
> recovery could be very short. That will take some thought on how to
> resolve.
>
> I have other things pressing on me now, but I'll add this to my todo,
> though I'll be relying on you to test it when I get round to it.
>
> --
> Simon Riggs
> EnterpriseDB http://www.enterprisedb.com
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
