Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uU5k3-00FRT4-Jm for pgsql-general@arkaria.postgresql.org; Tue, 24 Jun 2025 15:39:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uU5k0-00DEEJ-EU for pgsql-general@arkaria.postgresql.org; Tue, 24 Jun 2025 15:39:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uU5jz-00DEEB-Uz for pgsql-general@lists.postgresql.org; Tue, 24 Jun 2025 15:39:20 +0000 Received: from mail-oo1-xc2a.google.com ([2607:f8b0:4864:20::c2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uU5jy-003qgv-1u for pgsql-general@postgresql.org; Tue, 24 Jun 2025 15:39:20 +0000 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-6115f7ebf2fso313314eaf.3 for ; Tue, 24 Jun 2025 08:39:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750779557; x=1751384357; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=beEkse8iRZPDQFGFKLli7NX53tYldFb2WxrjQvIFryE=; b=f2SeHpZfCOsjYaklNXWYQpNJJWjNicQ/C3wUyLhtSkfCjywv8BAGWhZc+c6XmtrWAd a2tu/UkOJSDJA0pqK9L5+5jJ0jMxDDyCdc1cU28WqzxMkOvr3FDVe/gJcfGpXbL6q0sT pTYbX+ns6KMwFhay88Dmz0ot2EPx/0qnT6N8YVjxjZu0yBejyVigK3DqEYHKLkxYB2eH kdlle1UCinq35sFTHn/3C7UfOjih318fUN5az7ROWXXEEyRvYJ77LkRw74bLAbm6hLZ9 vGulyMYL07nMQPA+RD+y4Z66VJcBJ6pCCnUsHvL/Z5nv31NgSyTHES9RT2Ihw1xJ+TAo PYgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750779557; x=1751384357; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=beEkse8iRZPDQFGFKLli7NX53tYldFb2WxrjQvIFryE=; b=oYfqsGfLno8uBuAvbwd/gXmB7qHjJbiFWr1xpjmbodrko1nrG6sAByMCM5pJS4sQMb MamwXURqBtSFBl+rvtrTz/hD5RDHaWXCwbo0Ihnf8qT1upM4ZSTzkTMN1pVDZGO4lghJ EVToma8O1SeEMJ3EQg02iO1jPa1OO6Bg8ZzjTS1J/nw+r+8P5Dp+Fi2mQekKQAb8qmnY oNFYmSoK/HdLWClrKnbddAo2/t1GQ/yMygyvxmPCI/kk2D9OgViWYL7QZ8cdwe41qR+K LFwr0pAVOkBphqaxn0wI/lVkfESOU/qvtqGfxgT1ptvk0zfnFamwlIe2VzjAwaqV6+o8 i1bA== X-Gm-Message-State: AOJu0Yx72xc7EP8oZrbQLTst1ssPnePznZe0uVStnOnDqBWimqwMgULf /Gpc7zomvaCXpN6Y1b1nsesRyPrvdbJY2TR0czJnn8lwviEckm+mYaUXDqbgVRBz3SdvuU4ibHl /iQlOC4GdGgqhtejAFxX0snCXtuPT+lw= X-Gm-Gg: ASbGnct1xtJwYW4cmmtYacAfkafOfa3djPhABzWrEgIf+gCABazBqoIa1QlIEsYFvMZ wRm6pGHgRYyaBAivne6fir1JOZlScA2P3Su4RPBC0P+w5u+d+5wTfaxePy3X3o27jptafjAL80p mDIZGc+t9yvn8/rWWdbL/D+y8xZIQAHQys5UZyq32zrJE= X-Google-Smtp-Source: AGHT+IGkjwOut5qrWwVrklxj5biTSPyddwgXri04+m0Dgvh5VDGWa7D2pD7wqZh3hkxPY3q6mG8Ply/maoLUtNPUsNI= X-Received: by 2002:a05:6820:2910:b0:611:7385:77a0 with SMTP id 006d021491bc7-61173857c81mr8138003eaf.4.1750779556619; Tue, 24 Jun 2025 08:39:16 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kouber Saparev Date: Tue, 24 Jun 2025 18:38:59 +0300 X-Gm-Features: AX0GCFsvqom3ooQseDv2fk2gafPtG0Iw2Jcv7nVfn-xK-PlTL6oIjvO00iWuIe8 Message-ID: Subject: Re: pg_combinebackup failure To: Adrian Klaver Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000008d6a3f06385321ee" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008d6a3f06385321ee Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Barman is involved indeed, its version is 3.14. The command: "barman backup xxx --incremental latest". PostgreSQL is version 17.3. =D0=9D=D0=B0 =D0=B2=D1=82, 24.06.2025=E2=80=AF=D0=B3. =D0=B2 18:26 Adrian K= laver =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0: > On 6/24/25 02:31, Kouber Saparev wrote: > > Hello, > > > > We are trying to use pg_combinebackup but eventually it fails with: > > What is the command you are using to take the incremental backups? > > What version of Postgres are you taking the incremental backups from? > > Given the naming below, is Barman involved in this? > > If Barman is involved what version and what command is being used? > > > > > pg_combinebackup --debug --dry-run > > --output=3D/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 > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --0000000000008d6a3f06385321ee Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Barman is involved indeed, its version is 3.14. The comman= d: "barman backup xxx --incremental latest".

P= ostgreSQL is version 17.3.

=D0=9D=D0=B0 =D0=B2= =D1=82, 24.06.2025=E2=80=AF=D0=B3. =D0=B2 18:26 Adrian Klaver <adrian.klaver@aklaver.com> =D0= =BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0:
On 6/24/25 02:31, Kouber Saparev wrote:
> Hello,
>
> We are trying to use pg_combinebackup but eventually it fails with:
What is the command you are using to take the incremental backups?

What version of Postgres are you taking the incremental backups from?

Given the naming below, is Barman involved in this?

If Barman is involved what version and what command is being used?

>
> pg_combinebackup --debug --dry-run
> --output=3D/barman-backup/barman-data/test_combine 20250616T140003/dat= a
> 20250617T090005/data
>
> ...
>
> pg_combinebackup: would copy
> "20250616T140003/data/base/16420/2136674204" to
> "/barman-backup/barman-data/test_combine/base/16420/2136674204&qu= ot;
> pg_combinebackup: would copy
> "20250616T140003/data/base/16420/2542449085" to
> "/barman-backup/barman-data/test_combine/base/16420/2542449085&qu= ot;
> 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

--
Adrian Klaver
adrian.klave= r@aklaver.com

--0000000000008d6a3f06385321ee--