Robert Mu

Yes, we are discussing WAL_DELTA backups.

I have three commits to fix ‘delta map’ based delta backup. The first PR is https://github.com/wal-g/wal-g/pull/1861, and this is the second PR. Based on my testing, when all three PRs...

I'm going to bed now. Tomorrow I'll check if this issue is related to #1296.

I believe the issues I found are specifically related to delta file handling in WAL-G's delta backup system, and appear to be unrelated to the potential data corruption reported in...

You mean that with the current problematic code, in most cases delta files cannot be uploaded correctly, unless during full backup we happen to be at a WAL file where...

Based on my understanding of the code [`getDeltaMap`](https://github.com/wal-g/wal-g/blob/master/internal/databases/postgres/delta_map_downloader.go#L9-42), * wal-g only downloads and parses WALs managed by the local delta file(incomplete). This is because it hasn't accumulated enough WAL parsing...

In PostgreSQL 14 that I tested, backup history files are archived by PostgreSQL's archival process using the archive command. However, our `wal-g wal-push` command doesn't handle this scenario, which causes...

Good catch! However, I want to point out that in the scenario you described, the issue would actually fail at step 1. Here's why: When WAL segments xxxxxx01 and xxxxxx02...

I believe this scenario you described should not exist. If backup1 is marked as successful but WAL segments xxxxxx01 and xxxxxx02 are still being archived, it indicates that backup1 has...

1. It seems that you consider the example to be inappropriate. When a PostgreSQL database is started for the first time, no matter how many times backups are taken afterward,...