Nikolay Antonov

I am quite busy these days. Will try to reproduce issue tomorrow. As I can see - you asking `wal-g` to restore following combo: 1. stream_20250809T220002Z (base backup) 2. stream_20250809T230002Z...

Ok. Re-read source code... currently `wal-g` requires GTIDs to be enabled - that is how MySQL will skip events it already seen. Assumption that we have `GTID = ON` was...

> Another thing that Im not sure is whether it is okay to read the `xtrabackup_binlog_info` on walg code because AFAIK wal-g only uses data/files stored on the remote storage...

> Isn't `binlog_name` already stored in backup metadata? The name is `BinLogStart`. No. You should trust `xtrabackup` in this case. wal-g can select positions before/after backup. However only `xtrabackup` knows...

> Yes. would work. We could start another thread if we want to support gtid disabled, though. Is there any reason not to enable GTIDs?

`makezero` is supported by golang-ci, so we can add it our linters. Also, there is similar linter `prealloc` linter (however authors notes that it is rarely impreove performance). PS: also...

Technically, it will be correct to close readers/writers. However golang garbage collectors should clean this up. Anyway, error in Encrypt() is fatal and application will exit almost immediately. Summary: I...