Forcing current WAL file to be archived - Mailing list pgsql-hackers

From Bruce Momjian
Subject Forcing current WAL file to be archived
Date
Msg-id 200607251451.k6PEpHS05827@momjian.us
Whole thread Raw
Responses Re: Forcing current WAL file to be archived  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Forcing current WAL file to be archived  (Hannu Krosing <hannu@skype.net>)
List pgsql-hackers
Where are we on these TODO items:
         o Allow point-in-time recovery to archive partially filled           write-ahead logs [pitr]
           Currently only full WAL files are archived. This means that the           most recent transactions aren't
availablefor recovery in case           of a disk failure. This could be triggered by a user command or           a
timer.
         o Automatically force archiving of partially-filled WAL files when           pg_stop_backup() is called or the
serveris stopped
 
           Doing this will allow administrators to know more easily when           the archive contains all the files
neededfor point-in-time           recovery.
http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php
         o Add reporting of the current WAL file, perhaps as part of           partial log file archiving

Seems they should be completed for 8.2.  I have only a /contrib version for
the last one.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: root/administartor user check option.
Next
From: Andrew Dunstan
Date:
Subject: buildfarm web extensions - help wanted