| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | james(dot)inform(at)pharmapp(dot)de |
| Subject: | BUG #18800: Error while using pg_combinebackup |
| Date: | 2025-02-07 23:30:49 |
| Message-ID: | 18800-8b51806e266e3ffa@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18800
Logged by: James Inform
Email address: james(dot)inform(at)pharmapp(dot)de
PostgreSQL version: 17.2
Operating system: Linux Debian
Description:
I use pg_combinebackup with --dry-run to check an incremental backup. So far
everything went fine for weeks but know I get the following error message:
/opt/pg/bin/pg_combinebackup --dry-run -o /exchange/recover
./20250117_235000_full ./20250208_001500_incremental
pg_combinebackup: error: file
"./20250208_001500_incremental/base/4043490/INCREMENTAL.4048177" has
truncation block length 243767 in excess of segment size 131072
pg_combinebackup: removing contents of output directory
"/exchange/recover"
What can I do to narrow the issue down or get around this error?
I use multiple PostgreSQL installations and I only encounter this of one
installation.
Can a somehow corrupt storage be the reason?
Cheers,
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | me nefcanto | 2025-02-08 05:28:22 | Bug in copy |
| Previous Message | David Steele | 2025-02-07 14:16:39 | Re: Bug in recovery of drop database? |