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 1sjK7w-00HJ3g-A9 for pgsql-general@arkaria.postgresql.org; Wed, 28 Aug 2024 14:58:28 +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 1sjK7u-006Lpf-DX for pgsql-general@arkaria.postgresql.org; Wed, 28 Aug 2024 14:58:26 +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 1sjK7c-006HiR-6E for pgsql-general@lists.postgresql.org; Wed, 28 Aug 2024 14:58:08 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjK7a-001rOo-5W for pgsql-general@postgresql.org; Wed, 28 Aug 2024 14:58:07 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-27012aa4a74so4063548fac.0 for ; Wed, 28 Aug 2024 07:58:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724857085; x=1725461885; darn=postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5W51mq6hAamY5CbRWW2q/hxh3WeXfvfv4r3cQH0EN4A=; b=FOVmtP26UJnhklsTmrg7lbHMliljMO4N4Yo0EVlg3EyWnMYMsNW9FbSj8BYJas/Dmx sOMTT8H67NqHDvnGyA4V9q6LHM+1Ln1wz3wQwlMCvFAwiYB90tyvXT9ZxEFZbUg4sL97 TJkA35aNPlNhhoTg7o1JzZdp50lOxAEdxfi7T9uSP7zoJ3Qfl8HQ5RTsRvJsUfLRDDeB fArK8xVh/svfGumi9nwZmb1QOwpO5bZetxfwonDCgy5DIoNzx7+0aIcQNwhYOmlcmruG FXBPU/u8li9xhc9B8KcCHkaUGoCGE73y+cDjXQCE7kAxVV0ODCg5uv7/yUa/BDaa5FRt Xd3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724857085; x=1725461885; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5W51mq6hAamY5CbRWW2q/hxh3WeXfvfv4r3cQH0EN4A=; b=cv6dGOjNLYcbGor7kFvxQ36oi7S7jailVfk/GfH6iBYIOIJMCy8CKTKBgS5fAUPQHH C/giul9JhasOTplQ4n0BtqqzX6Thx0B/b/QXeiWBc5zc73f28VmgutXqo76PNMw3fmir Qe2B5YQu88XkMKx7DYT7OnjTgYILM34W+eV/8N+h9wj8RSIhBpzDmyiPZHzlhCX+nEwK 5QXxniwHIya5PSVboipMmoBwuXnHpqpeKv7Lzmf120Pl3Wj6s/ngeYN+LY6PZhmdeJhb I9JJN0zN2KJwC3I6b1UPt+mZWkzb+Wy94o6ttBeugg+42UdwcsB0h0BMnFcZ7u54par0 8PaA== X-Forwarded-Encrypted: i=1; AJvYcCX87JKPLZlwcf2C/HGOtm/fE48HIH/N1aHdnZqAI77uC/geHx3EJEvW3qJcVmCELMliykUnJ9Yt75WenjPY@postgresql.org X-Gm-Message-State: AOJu0Yx5k8xe2x9iedZJOkvwJoOzOU4dkn4M+8gSFJ9woreNN2eYKwTe tpLc/6GOppwjnhsN0fU6oOf3NGWQO84DLA3jQ5309EXGID8pO4Z2olsxWXVM9ei/sI+0XZtCTjf SK7gfjOgXSEooOgRfrasQylfwzAq6uElD X-Google-Smtp-Source: AGHT+IGVgPzZai4i6wXlpS9X1i0l5ukCJtPaFY69K/bcHm2p+Pz5HcDn/OW6/YwXRbkTWJuv3aWOUXMkDQ0Rf2ep7Ac= X-Received: by 2002:a05:6870:8185:b0:260:f1a8:a64b with SMTP id 586e51a60fabf-273e64df945mr20939354fac.24.1724857085066; Wed, 28 Aug 2024 07:58:05 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:5e88:0:b0:557:c384:fb61 with HTTP; Wed, 28 Aug 2024 07:58:04 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Wed, 28 Aug 2024 07:58:04 -0700 Message-ID: Subject: Re: PgbackRest : Stanza creation fails on DB Server and Repo Server To: Amitabh Kant Cc: KK CHN , pgsql-general Content-Type: multipart/alternative; boundary="000000000000d807320620bf9502" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d807320620bf9502 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, August 28, 2024, Amitabh Kant wrote: > On Wed, Aug 28, 2024 at 8:00=E2=80=AFPM David G. Johnston < > david.g.johnston@gmail.com> wrote: > >> On Wednesday, August 28, 2024, KK CHN wrote: >> >>> >>> and I have .pgpass in DB server as >>> >> >> You assumed this mattered but I see no mention that pgBackRest consults >> this file. >> >> It seems to require the local entry in pg_hba.conf to use peer >> authentication. >> >> David J. >> >> > Section 21.4 on this page ( https://pgbackrest.org/user- > guide.html#introduction ) does seem to mention the use of .pgpass file. > I have no idea about the actual problem though. > Yes, postgres itself uses .pgpass so when you configure streaming replication between two servers, something that is doable regardless of using pgBackRest, the server-to-server connection can utilize .pgpass. David J. --000000000000d807320620bf9502 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, August 28, 2024, Amitabh Kant <amitabhkant@gmail.com> wrote:
On Wed, Aug 28, 2024 at 8:00=E2=80=AFPM Dav= id G. Johnston <david.g.johnston@gmail.com> wrote:
On Wednesday, = August 28, 2024, KK CHN <kkchn.in@gmail.com> wrote:

and I have=C2=A0 = =C2=A0.pgpass in DB server as=C2=A0

=
You assumed this mattered but I see no mention that pgBackRest consult= s this file.

It seems to require the local entry i= n pg_hba.conf to use peer authentication.

David J.=


Section 21.4 on this = page ( https://pgbackrest.org/user-guide.html#introduction = )=C2=A0 does seem to mention the=C2=A0use of .pgpass file. I have no idea a= bout the actual problem though.

Yes, postgres itself uses .pgpass so when you configure streaming re= plication between two servers, something that is doable regardless of using= pgBackRest, the server-to-server connection can utilize .pgpass.

David J.=C2=A0
--000000000000d807320620bf9502--