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.
I added some basic support of orioledb by wal-g
I tested that with these small modifications these features work:
Adding Dockerfile, scripts, and log of running this test to prove that it works
Sorry, that I'm not added it to pg_tests yet. Was not sure.
For now I added code to postgres wal-g version with option to enable it
Orioledb implemented as postgres extension with own table access method, and so it basically works alongside regular postgres, but uses own file format to store table pages
Without modification wal-g performs a full backup (with WALG_DELTA_MAX_STEPS=6)
wal-push and wal-fetch works because we implemented custom wal records, so no additional code required for this
I duplicated some functions with Orioledb* prefixed versions just to not affect any non-postgres related code for now
But I wan't to discuss before going any further what will be the better way to implement this
I see three variants:
What do you think?
Files:
ubuntu_check.log
wal-g-orioledb-test.zip