From: | Kouber Saparev <kouber(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | pg_combinebackup failure |
Date: | 2025-07-07 12:47:06 |
Message-ID: | CAN4RuQvqm0KK4qm+a-i8V6ap3b7Xf7t0G1phekGaMSL-0Gv0Lw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
We are using PostgreSQL 17.3 and Barman 3.14.0.
We are trying to use pg_combinebackup but eventually it fails with:
pg_combinebackup --debug --dry-run
--output=/barman-backup/barman-data/test_combine 20250616T140003/data
20250617T090005/data
...
pg_combinebackup: would copy "20250616T140003/data/base/16420/2136674204"
to "/barman-backup/barman-data/test_combine/base/16420/2136674204"
pg_combinebackup: would copy "20250616T140003/data/base/16420/2542449085"
to "/barman-backup/barman-data/test_combine/base/16420/2542449085"
pg_combinebackup: error: file
"20250617T090005/data/base/16420/INCREMENTAL.4085177931.76" has truncation
block length 9501840 in excess of segment size 131072
Any idea what's wrong?
--
Kouber Saparev
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2025-07-08 11:52:11 | REVOKE ALL ON ALL OBJECTS IN ALL SCHEMAS FROM some_role? |
Previous Message | Greg Sabino Mullane | 2025-07-04 13:45:55 | Re: Guidance Needed: Scaling PostgreSQL for 12 TB Data Growth - New Feature Implementation |