[ https://forge.continuent.org/jira/browse/SEQUOIA-419?page=all ]
Olivier Fambon closed SEQUOIA-419:
----------------------------------
Resolution: Fixed
Fix Version: Sequoia 2.10.7
Fixed in both 2_10 and 3_0 branches.
purge now clears the log up to specified dump checkpoint EXCLUDED.
purge now also clears checkpoints with older ids.
> "purge log" Command Does Not Remove Associated Checkpoint(s)
> ------------------------------------------------------------
>
> Key: SEQUOIA-419
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-419
> Project: Sequoia
> Type: Bug
> Components: Recovery Log
> Versions: Sequoia 2.8.1
> Environment: 1 Sequoia Controller (from CVS, checkout March 29/2006, 08:30
> PDT), 1 virtual database, 1 PostgreSQL 8.1 backend
> Reporter: Dylan Hansen
> Assignee: Jeff Mesnil
> Fix For: Sequoia 2.10.7, Sequoia 3.0 beta3
>
>
> Quoting an e-mail that was sent to the mailing list from Emmanuel:
> "You should never remove checkpoints. The checkpoints are hidden to the user.
> They will be automatically dropped when you remove a dump or resync/purge the
> recovery log."
> I have simple setup that I've performed 3 backups on (live backend), which
> has produced some checkpoints:
> testing(admin) > show dumps
> +---------+---------------------------------------------+---------------------+-------------------------------------+------------------+---------------------+--------+
> | Name | Checkpoint | Format
> | Path | Date | Backend
> | Tables |
> +---------+---------------------------------------------+---------------------+-------------------------------------+------------------+---------------------+--------+
> | backup3 | cp_for_backup3_Wed Mar 29 10:24:25 PST 2006 | PostgreSQL Tar Dump
> | /usr/local/sequoia/backups/testing/ | 3/29/06 10:24 AM | database1 | *
> |
> | backup2 | cp_for_backup2_Wed Mar 29 10:24:18 PST 2006 | PostgreSQL Tar Dump
> | /usr/local/sequoia/backups/testing/ | 3/29/06 10:24 AM | database1 | *
> |
> | backup1 | cp_for_backup1_Wed Mar 29 10:24:08 PST 2006 | PostgreSQL Tar Dump
> | /usr/local/sequoia/backups/testing/ | 3/29/06 10:24 AM | database1 | *
> |
> +---------+---------------------------------------------+---------------------+-------------------------------------+------------------+---------------------+--------+
> testing(admin) > show checkpoints
> Checkpoints...
> [0] cp_for_backup1_Wed Mar 29 10:24:08 PST 2006
> [1] cp_for_backup2_Wed Mar 29 10:24:18 PST 2006
> [2] cp_for_backup3_Wed Mar 29 10:24:25 PST 2006
> [3] Initial_empty_recovery_log
> Lets say that I want to purge the log up to backup3. What I'm assuming this
> should do is remove all checkpoints previous to the checkpoint that is
> assoicated with the backup we're purging the log to. However, this is not
> the case:
> testing(admin) > purge log backup3
> testing(admin) > show checkpoints
> Checkpoints...
> [0] cp_for_backup1_Wed Mar 29 10:24:08 PST 2006
> [1] cp_for_backup2_Wed Mar 29 10:24:18 PST 2006
> [2] cp_for_backup3_Wed Mar 29 10:24:25 PST 2006
> [3] Initial_empty_recovery_log
> The log entries are removed, however the checkpoints still remain.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
