From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Forcing current WAL file to be archived |
Date: | 2006-07-25 14:51:17 |
Message-ID: | 200607251451.k6PEpHS05827@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 available for 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 server is stopped
Doing this will allow administrators to know more easily when
the archive contains all the files needed for 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(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-25 15:07:50 | Re: Forcing current WAL file to be archived |
Previous Message | Andrew Dunstan | 2006-07-25 14:47:18 | Re: root/administartor user check option. |