Thanks Israel for these informations. In fact, I thought at first of a problem related to the version of pg_basebackup in version 17. I should have posted first on the barman github.Best regards,FabriceOn Wed, Jul 30, 2025 at 12:47 AM Israel Barth Rubio <barthisrael@gmail.com> wrote:Hello Fabrice,> But I do not understand this error with the barman wrapper:> > Backup completed (start time: 2025-07-26 21:45:07.238223, elapsed time: 19 seconds)> Waiting for the WAL file 0000000300000B3F0000000C from server 'x_service' (max: 600 seconds)> Processing xlog segments from streaming for x_service> 0000000300000B3F0000000A> Processing xlog segments from streaming for x_service> 0000000300000B3F0000000B> ERROR: The WAL file 0000000300000B3F0000000C has not been received in 600 secondsAre you by chance running PostgreSQL 17?If you are using PostgreSQL 17, you are very likely encountering the issuetracked here: https://github.com/EnterpriseDB/barman/issues/1041. In that case,a fix has already been merged and will be included in an upcoming release ofBarman.As a quick note for the future, the Barman GitHub issues page is the correct placeto report problems like this directly to the development team. In any case, I understandthat you raised it here given the context of the original question about pg_basebackup.Hope that helps you.Best regards,Israel.
Hello Fabrice,> But I do not understand this error with the barman wrapper:> > Backup completed (start time: 2025-07-26 21:45:07.238223, elapsed time: 19 seconds)> Waiting for the WAL file 0000000300000B3F0000000C from server 'x_service' (max: 600 seconds)> Processing xlog segments from streaming for x_service> 0000000300000B3F0000000A> Processing xlog segments from streaming for x_service> 0000000300000B3F0000000B> ERROR: The WAL file 0000000300000B3F0000000C has not been received in 600 secondsAre you by chance running PostgreSQL 17?If you are using PostgreSQL 17, you are very likely encountering the issuetracked here: https://github.com/EnterpriseDB/barman/issues/1041. In that case,a fix has already been merged and will be included in an upcoming release ofBarman.As a quick note for the future, the Barman GitHub issues page is the correct placeto report problems like this directly to the development team. In any case, I understandthat you raised it here given the context of the original question about pg_basebackup.Hope that helps you.Best regards,Israel.
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных