Bagger producer #86
Open
Bagger producer #86
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
for different tables
written to the last column
…ition (now it's based on written data size, not the number of messages)
…buffer flush in bagger_commit_worker
additionally escapes all backslashes. This makes it safer for text COPY format. Though it might be slower too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A special producer for bagger and compressed storage. Because of the implementation of
pg_cryogenit works at its best when large batches of data are inserted. Currentpostgres produceron the other hand inserts tuples into a master table which then routes those tuples to partitions.Bagger producer maintains internal buffers for each partition involved and flushes them as large batches when reaches size or delay threshold. This approach also makes master table and trigger obsolete. I haven't benchmarked it yet, but i expect that it might give a massive performance boost.
Bagger producer is based on
exports producerand naturally inherits its features. Particularly it allows to split a large json into several smaller ones or extract some fields into separate columns.