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

Thoughts on enabling support for s3/remote storage? #3

Open
pbrumm opened this issue Mar 5, 2013 · 1 comment
Open

Thoughts on enabling support for s3/remote storage? #3

pbrumm opened this issue Mar 5, 2013 · 1 comment

Comments

@pbrumm
Copy link

pbrumm commented Mar 5, 2013

I recently implemented wal-e for postgres, and it's s3 storage and restore are very compelling.

@basak
Copy link
Owner

basak commented Mar 14, 2013

I have no problem in principle. An issue might be that although individual chunks work well with S3's object store paradigm, the sqlite3 database that maintains chunk sequencing does not. An initial implementation might have to first download the sqlite3 database to a temporary directory, work on it there, upload chunks from S3 such that the S3 archive maintains integrity, upload the modified sqlite3 database back up to S3, and then delete any chunks at that point (to maintain integrity).

Further changes might be to support per-chunk HMAC and encryption.

But I don't think this is trivial. No objection in principle, though.

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

No branches or pull requests

2 participants