To note effectively that the problem comes from a fix in version 17 PostgreSQL: Release Notes <https://www.postgresql.org/docs/release/17.0/>
Change file boundary handling of two WAL file name functions (Kyotaro Horiguchi, Andres Freund, Bruce Momjian) Regards, Fabrice On Wed, Jul 30, 2025 at 10:33 AM Fabrice Chapuis <fabrice636...@gmail.com> wrote: > 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, > > Fabrice > > On Wed, Jul 30, 2025 at 12:47 AM Israel Barth Rubio <barthisr...@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 seconds >> >> Are you by chance running PostgreSQL 17? >> >> If you are using PostgreSQL 17, you are very likely encountering the issue >> tracked 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 >> of >> Barman. >> >> As a quick note for the future, the Barman GitHub issues page is the >> correct place >> to report problems like this directly to the development team. In any >> case, I understand >> that you raised it here given the context of the original question about >> pg_basebackup. >> >> Hope that helps you. >> >> Best regards, >> Israel. >> >
