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.

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

Updates in caching behaviour #3258

Closed
binaek opened this issue Mar 23, 2023 · 0 comments · Fixed by #3266
Closed

Updates in caching behaviour #3258

binaek opened this issue Mar 23, 2023 · 0 comments · Fixed by #3266
Assignees

Comments

@binaek
Copy link
Contributor

binaek commented Mar 23, 2023

  • STEAMPIPE_CACHE environment variable resolves to service cache enabled as well as client cache enabled
  • service cache enabled is used by the plugin manager to enable/disable caching on the plugins during startup (runtime toggle is not allowed) - with a max_ttl
  • client cache enabled is used to enable/disable the cache on the database connection (fdw)

A TTL can also be set on the client side capped to max_ttl on the server

@binaek binaek self-assigned this Mar 23, 2023
@binaek binaek linked a pull request Mar 24, 2023 that will close this issue
kaidaguerre pushed a commit that referenced this issue Mar 31, 2023
…erver. Closes #3258

STEAMPIPE_CACHE environment variable resolves to service cache enabled as well as client cache enabled

service cache enabled is used by the plugin manager to enable/disable caching on the plugins during startup (runtime toggle is not allowed) - with a max_ttl

client cache enabled is used to enable/disable the cache on the database connection (fdw)
A TTL can also be set on the client side capped to max_ttl on the server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant