timescaledb-wale icon indicating copy to clipboard operation
timescaledb-wale copied to clipboard

Migration to wal-g

Open edusperoni opened this issue 3 years ago • 1 comments

I was trying out wal-g mainly for the extra compression options. Any chance this can be updated to use wal-g?

I can open a PR for it, as I already implemented it (https://github.com/edusperoni/timescaledb-wale) (edusperoni/wal-g on dockerhub).

The only breaking change is that I had to remove these lines of code:

WALE_S3_PREFIX=${WALE_S3_PREFIX:-s3://${WALE_S3_BUCKET:-wale_bucket}/${WALE_S3_PATH:-}}

export WALE_S3_PREFIX

because if those are present, wal-g always tries to upload to S3 instead of locally, even if the s3 url is invalid and WALE_FILE_PREFIX is defined.

We can also symlink /usr/loca/bin/wal-e to /usr/loca/bin/wal-g to reduce the amount of breaking changes as well.

edusperoni avatar Jan 12 '22 14:01 edusperoni

hi legend i try to clone your wal-e feat wal-g codes to run docker build, got error message "cloud.google.com/go/[email protected]: Get "https://proxy.golang.org/cloud.google.com/go/storage/@v/v1.8.0.mod": x509: certificate signed by unknown authority", how can i fix this issue? thanks

pythonlhugithub avatar May 03 '24 03:05 pythonlhugithub