fix(clickhouse): [WRA-5] refactor data scan with async streaming #515
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.
What kind of change does this PR introduce?
This PR is to refactor ClickHouse FDW data scan to use async streaming.
What is the current behavior?
Currently, the ClickHouse FDW uses
fetch_all()to read the whole result data set from ClickHouse to local memory, and then convert them to Postgres rows. This approach doesn't limit memory usage and it will exhaust local memory if the result data set is large.What is the new behavior?
Refactored the data scan to use async worker based streaming. The result data set is asynchronously read from ClickHouse by a dedicate thread, and then converted and transmit to Postgres through a buffered sized-limited (1024 by default) channel. By using this streaming approach, the local memory usage will be restricted by the size of channel, thus memory exhaustion will be prevented.
Additional context
N/A