| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Kouber Saparev <kouber(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_combinebackup failure |
| Date: | 2025-07-23 10:41:48 |
| Message-ID: | CAKoxK+6mEwEFSwR9YkzL2qPAirJFg3MSiB9cDsJ09mzcTYKfkA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Jul 7, 2025 at 2:47 PM Kouber Saparev <kouber(at)gmail(dot)com> wrote:
>
> 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
>
I don't think combining barman and PostgreSQL basebackups is a good
idea. While barman does use pg_basebackup (I don't think it uses the
incremental feature, yet), it could have done some relinking after the
backup has been taken (of some other stuff).
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2025-07-23 19:50:15 | problem with MERGE command? |
| Previous Message | Laurenz Albe | 2025-07-18 06:16:21 | Re: VACUUM FREEZE vs plain VACUUM |