From: | "Campbell, Lance" <lance(at)illinois(dot)edu> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Error when running pg_basebackup |
Date: | 2016-10-12 19:31:29 |
Message-ID: | B75CD08C73BD3543B97E4EF3964B7D7047910C1D@CITESMBX1.ad.uillinois.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
PostgreSQL - 9.5.4
Command that is being executed:
pg_basebackup --host=localhost --xlog --gzip --write-recovery-conf --format=t --pgdata=${BACKUPS_HOME}/${BACKUP_DATE_TIME}
Error message that appears at the very end of pg_basebackup:
pg_basebackup: could not get transaction log end position from server: ERROR: requested WAL segment 00000001000001CD00000055 has already been removed
When pg_basebackup runs at the very end it will put in your archive log folder an archive WAL file that ends in ".backup". This is intended as a marker. The WAL file segment that is referenced in the error message is always the WAL segment prior to the ".backup" marker. This happens every time I run pg_basebackup.
How can I prevent this error from occurring?
Thanks,
Lance
From | Date | Subject | |
---|---|---|---|
Next Message | Lazaro Garcia | 2016-10-12 20:04:11 | Re: Is Bi-Directional Replication (BDR) is fully integrated into PostgreSQL 9.6 or 9.7? |
Previous Message | Alex Balashov | 2016-10-12 19:10:47 | Re: Is Bi-Directional Replication (BDR) is fully integrated into PostgreSQL 9.6 or 9.7? |