add --since and --until to "pg export" #17
Conversation
This file contains 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
…insert of features as bulk
|
Any progress? I have the same use case. |
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.
It is useful to have a postgres mirror, which reflects the current state of a geogig repo. This currently requires to do a complete export of the entire dataset after every change, which takes about 3/4 of a hour for our production datasets.
This pull request contains support for the two Parameters --since and --until. They take a commit references as argument. A diff between the commits is computed and respective inserts and deletes are done on the database(modify is done as delete followed by insert). The speed of the export only depends on the number of changed elements. For small changes the Export is nearly instant.