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 1vBs4z-006GPy-AZ for pgsql-admin@arkaria.postgresql.org; Thu, 23 Oct 2025 09:57:56 +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 1vBs4x-007uVX-VL for pgsql-admin@arkaria.postgresql.org; Thu, 23 Oct 2025 09:57:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vBs2V-007q0s-Sn for pgsql-admin@lists.postgresql.org; Thu, 23 Oct 2025 09:55:22 +0000 Received: from mail-lj1-x22c.google.com ([2a00:1450:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vBs2T-003KPp-0f for pgsql-admin@postgresql.org; Thu, 23 Oct 2025 09:55:21 +0000 Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-378d65d8184so7810121fa.0 for ; Thu, 23 Oct 2025 02:55:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataegret.com; s=google; t=1761213319; x=1761818119; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=1JJgaou3srs25Lb74Osc4ltPn+sgcAXn2kJgTgX4Hhg=; b=okqrxGc9v7fOLH+N+jODD/1zDJ10xeMFlRzv4vi5egaUQFxtHB272OqZk/ozR6Q20V PDBdonBxEDZjgjF84uByFfw8ZirkN9WNiSYJoQZV+dNgodnGWHA8nD8pRePsruiIb4Lg 6eZ8ZSfTXFmyqKONAgH0wX7xpJsx7HLmWoJjk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761213319; x=1761818119; h=content-transfer-encoding:cc:to:subject:message-id:date:from :reply-to:in-reply-to:references:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=1JJgaou3srs25Lb74Osc4ltPn+sgcAXn2kJgTgX4Hhg=; b=tIzUl2XC1/Ru+h2K9PLT8e0l476ppbPEeC1gZrR5TenAO+EE/a7CZd0mY3nLHZ5Sck EIpvg4mucmVS/HTEWpT++mBcPuXqRZ2/uUe8ASlyKBHR/gc+gqunqAWGlgnjdmEaMBKh oRrCDEyEH+bQpqJG/T+LogAADxZjQSRc2ROR4458IW+Y9OVqym/Hu2AlF+DizOIAzDar rP+NSSm2PrORYzSob3xtp4F9y0Q8BV4GK0mr/olwtf7oSNFYSGcBR8/iOMNGKZtu5rkI R/eMLHMjzs9BmMdNV08cGBZ3j+4Qa5pk1yWSE4GEdmTHCX9uYTu9c9/1HqKk3bTe+4LY cIPQ== X-Gm-Message-State: AOJu0Yz1JpkclMiygpSe4KAmiJAzyk28mTNywAARsMeGt2Rt3qYNBqZH accyRa5DmDGopGOvRgYPSoKyOjy/xHYMoedRDVY/XZMMn7LTjTNBjhfyX04eZEg6XMSjTXMlQAN WGr9bfmQt3fw4k+Tr2JIDDONYjs0N65PsJRRjicrf X-Gm-Gg: ASbGnctW9srZuvmIa05qNrEMJudWrcAX2qgMMvMUVC9ikMhjipPptBbPxQS28duGubC HKMzFTrGX2RQtPTH8Vz61blC5VQUPZDa/JzgQRh78IeWhMiNywxCG6MgN9UpXGMXtMgrToAMVWq djntKFYfkFDY4rlGrdXtdYGU6cqC9JogoA9lsoDqqnUw3AwWmyaLzQ2oH+L8ciT8BKLE6Xsfs5P oZuEqFIt0dqMZuxEidFq1NAlNSQM9GlMlbVue3wH2aTN8kfkW7TLm+ENjPygUMpKAs8ZA== X-Google-Smtp-Source: AGHT+IEmgdmgJbJmVhsgepDwqO/2IkGlDkyKD0+tsltsmUM76rPU8EiOn9EcwkKNXE4cnwFUSqyQhDeno+gnIATVhSM= X-Received: by 2002:a05:651c:b25:b0:36d:501:76d7 with SMTP id 38308e7fff4ca-377978c14acmr73866731fa.14.1761213319018; Thu, 23 Oct 2025 02:55:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: ik@dataegret.com From: Ilya Kosmodemiansky Date: Thu, 23 Oct 2025 11:54:42 +0200 X-Gm-Features: AS18NWC-5Mb280d_2BnkHDVKcD8EUaWyuVme_FiRXQy3Y49EzKC8TDSlp1yUKjo Message-ID: Subject: Re: PGbackrest very slow! To: =?UTF-8?Q?P=C3=A4r_Mattsson?= Cc: pgsql-admin Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi P=C3=A4r, On Thu, Oct 23, 2025 at 10:59=E2=80=AFAM P=C3=A4r Mattsson wrote: > > Hi! > I have 3 node postgres cluster with repmgr and pgpool. > > Pgbackrest is configed like this > We use pgbackrest with this config > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D It is a quite basic config, > It is not a network issue. I tested to transfer 2GB between two host and = it took 4 sec. > > > I think backup-standby=3Dy slows down the backup out of all minds. > so if you are sure it is not a network issue, your guess could be right. You can try to compare with backup from primary and if it is faster, it could be archiving process on standby which slows you down. You can try to improve it with more processes [1] and with better zst compression [2]. Async archiving [3] could also help > > Br P=C3=A4r > > [1] https://pgbackrest.org/configuration.html#section-general/option-proces= s-max [2] https://pgbackrest.org/configuration.html#section-general/option-compre= ss [3] https://pgbackrest.org/configuration.html#section-archive/option-archiv= e-async best regards, Ilya Kosmodemiansky CEO, Founder Data Egret GmbH Your remote PostgreSQL DBA team T.: +49 6821 919 3297 ik@dataegret.com