-
-
Notifications
You must be signed in to change notification settings - Fork 179
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.
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
Add cache configuration #1137
Comments
I would like to add that a common use case for caching with tile servers is to have Z-level specific caching. For example, large datasets at low zoom levels are very expensive, but at high zoom levels they are really cheap, so it would be nice to be able to say something like : "for data_source_a I want to cache zoom levels from 0-5 only, but for data_source_b I want to cache zoom from 0-9" |
Additionally, cache invalidation rules...we should be able to specify a TTL at the very least. An ideal-world scenario, but obviously far more complex is cache invalidation that happens in sync with the database via LISTEN/NOTIFY updates via trigger functions attached to tables. |
This would be amazing to have. In my case, users need to update specific geometries so when that happens the cache needs to be busted. Right now I need to choose between all or northing. |
Each tile source cache should be configurable, at least to be able to selectively enable/disable cache, but possibly more advanced.
Steps:
cache=enable|disable|auto
. Theauto
setting (default) should be the same asenable
for now, but may become more complex in the future.The text was updated successfully, but these errors were encountered: