-
Notifications
You must be signed in to change notification settings - Fork 433
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
New pre-release/incremental release? #970
Comments
Hi! |
We would appreciate new release also |
Ok, here's the pre-release if you wish to try out the current version. |
@x4m I'm going to build and test pre-release, thanks. We're missing bug fix for #840 and we're currently trying to make it work together with https://github.com/sorintlab/stolon/blob/master/doc/pitr_wal-g.md. Unfortunately restore to point-in-time doesn't work for me when I specify exact date and time (it works great when I restore to the latest state) so I'm trying to dig and understand is it stolon or wal-g issue. After I'll figure out this I can help you with release preparation if you need. |
v0.2.22 looks good. Created separate issue (for PiTR), in the meantime I looked through the diff and found interesting features/fixes (at least from my perspective).
|
meanwhile I understood that problem wasn't in wal-g, but lack of knowledge about PostgreSQL! @x4m how can we proceed?:) |
I'm happy to see that a new release is planned. With 0.2.19, restoration is not working from s3 like service because pagination on list object v2 is broken. The following merge request should fix the issue and is included since 0.2.20 |
@agadelshin @Vampouille this looks like decent release notes, many thanks! |
Thanks, everyone! v1.0 released |
Would it be possible to get a new incremental/"pre-release" release for further testing of:
wal-g/storages#45
The last pre-release (https://github.com/wal-g/wal-g/releases/tag/v0.2.21) was made the day before the above PR was merged, so I've been running on internal builds at $DAYJOB without issue. That said, I'd rather point back to upstream if possible for long-term use. =)
Also, there was mention of moving storages back under wal-g (wal-g/storages#15 (comment)), so I don't know if that is a current blocker or not. Please advise if there's anything I can do to assist if that is still planned.
Thanks!
The text was updated successfully, but these errors were encountered: