Hello all!

I enabled + deployed PITR for my Postgres instance, and despite the logs appearing to confirm that 1/ a full backup exists and 2/ WAL files are being pushed every minute, Railway appears to think that is not the case, as I keep getting this error:

No coverage yet — waiting for the first WAL segment to archive and base backup to complete. Usually ready within a few minutes.

The logs show that indeed, very quickly after the image was online, a ful back up did happen.

pgbackrest-watcher: running pgbackrest backup --type=full
[...] full backup size = 85.2MB, file total = 1491
backup command end: completed successfully (12953ms)
pgbackrest-watcher: backup --type=full completed
pgbackrest-watcher: pitr anchor emitted
[...]
pgbackrest-watcher: verifying S3 catalog has full backup
pgbackrest-watcher: catalog verified — full backup present in S3
pgbackrest-watcher: iteration: no action (last_full=1780684583, archived=4, failed=0, gap_marker=absent, gap_state=clear, last_full_failed=0, lag=0)

And WAL files are being pushed every minute:

archive-push command begin 2.58.0: [pg_wal/000000010000000000000045] [...]
pushed WAL file '000000010000000000000045' to the archive asynchronously
archive-push command end: completed successfully (604ms)

Am I missing or misunderstanding something here? I'm fairly new to Railway, and I'm definitely not a Postgres expert in any way.

Project ID: 5a840562-4bab-48b2-95c1-23296e054960

Environment ID: 4d442772-e1f0-42be-b619-e7abe942cce7