db: Skip backup of gps_points table data#856
Open
Firefishy wants to merge 1 commit into
Open
Conversation
Member
Author
|
For consideration if we want to do this... |
Collaborator
|
I'm fine with this. pg_dump isn't for backups anyways, that's what a base backup + WAL is for. |
Member
Author
We don't currently do base backups. |
Member
|
If we move to base backups then we can go further than this PR and exclude all tables (like the history tables!) that the planet dump doesn't need. |
ceacc16 to
7f6aecb
Compare
Collaborator
Unfortunately it needs those for the history PBF :( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Skip the backup of
gps_pointstable data.The
gps_pointstable data could be re-imported from the source GPX files.The
gps_pointstable data bloats the backup size and directly delays the publishing of the planet data.