Add build for proxy on PostgreSQL #1748
Closed
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
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.
This adds the build framework for a PostgreSQL proxy. It does NOT yet allow for TimescaleDB specific capabilities, but we're working on that (i.e., things like partition-based housekeeping in the source-code repo). However, it will work for (stock) PostgreSQL images.
I know there was a previous request to add this support that was closed (#435), saying it's redundant. However, I believe that housekeeping can become a bottleneck for larger proxies (the same way it is for servers), and partition-based housekeeping can provide a huge benefit. This is the starting point / basis for adding such support.