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

Add Query Cache support for PostgreSQL #4689

Open
rahim-kanji opened this issue Oct 1, 2024 · 0 comments · Fixed by #4703
Open

Add Query Cache support for PostgreSQL #4689

rahim-kanji opened this issue Oct 1, 2024 · 0 comments · Fixed by #4703
Assignees

Comments

@rahim-kanji
Copy link
Collaborator

Issue Description:

Currently, ProxySQL lacks support for query caching for PostgreSQL, a feature that could greatly enhance performance for frequently executed read queries. MySQL has query cache support in ProxySQL, but this functionality is not yet extended to PostgreSQL connections.

Expected Feature:

  • Introduce query cache support for PostgreSQL within ProxySQL, configurable via query rules, similar to the existing support for MySQL.
  • Cache SELECT queries according to user-defined query rules, allowing selective caching of frequently executed queries based on specific patterns or conditions.
  • Provide configurable options for cache size, TTL (Time-To-Live), and invalidation policies.

Benefits:

  • Enhanced Performance: Caching the results of frequent SELECT queries can significantly reduce the load on the PostgreSQL backend, leading to faster response times.
  • Flexible Control: Using query rules allows database administrators to control which queries are cached, optimizing the cache for the most impactful use cases.
  • Resource Efficiency: Reduces CPU and disk I/O overhead by serving cached results for repeated queries, optimizing resource usage on the PostgreSQL server.

Configuration Options:

  • Query Rules for Caching: Query rules can define which queries are cached based on patterns, query types, or other conditions.
  • Cache Size: Configure memory allocation for query caching.
  • TTL (Time-To-Live): Define how long cached query results should persist before expiration.
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