Add max_tiles_per_run setting for tile generalizers #2450
Conversation
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
The TRUNCATE didn't work, because there can be tiles from more than one zoom level in the same table. Using DELETE ... RETURNING we are ensured to always delete exactly what we are getting back.
Limits the number of tiles for which the generalizer is run. Used when generalization is too expensive to always run for all expired tiles. There is a good chance that later changes in the data affect the same tile again, so in the long run this saves effort. Tiles are generalized oldest first when this is used. Don't set max_tiles_per_run or set to 0 to run generalization for all tiles in the expire table for that zoom level.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Limits the number of tiles for which the generalizer is run. Used when generalization is too expensive to always run for all expired tiles. There is a good chance that later changes in the data affect the same tile again, so in the long run this saves effort.
Tiles are generalized oldest first when this is used. Don't set
max_tiles_per_runor set to 0 to run generalization for all tilesin the expire table for that zoom level.