Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dumptablespace: ensure dumped data is read from the expected log position #63

Closed
eolivelli opened this issue Jan 17, 2017 · 2 comments
Closed

Dumptablespace: ensure dumped data is read from the expected log position #63

eolivelli opened this issue Jan 17, 2017 · 2 comments
Assignees
@eolivelli
Labels
bug

Comments

@eolivelli
Copy link
Contributor

No description provided.

@eolivelli eolivelli added the bug label Jan 19, 2017
@eolivelli
Copy link
Contributor Author

Idea from @diegosalvi @aluccaroni : we can bundle in the backup file the portion of transaction log from the start of the checkpoint to the end of the checkpoint, this way the 'restore' will act exactly as the 'replica' which boots, that is:

  • download a snapshot of the tablespace
  • apply the transaction log, for each table apply only the part of the log not already included in the snapshot

@eolivelli eolivelli self-assigned this Jan 23, 2017
@eolivelli
Copy link
Contributor Author

close by commit c84a870

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@eolivelli eolivelli

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eolivelli