From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Amitabh Kant <amitabhkant(at)gmail(dot)com> |
Cc: | KK CHN <kkchn(dot)in(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PgbackRest : Stanza creation fails on DB Server and Repo Server |
Date: | 2024-08-28 14:58:04 |
Message-ID: | CAKFQuwax7xHofBW+phfbPDweGoqvf1BWbVwSVDKJTemR249LOg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday, August 28, 2024, Amitabh Kant <amitabhkant(at)gmail(dot)com> wrote:
> On Wed, Aug 28, 2024 at 8:00 PM David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Wednesday, August 28, 2024, KK CHN <kkchn(dot)in(at)gmail(dot)com> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Biesinger | 2024-08-28 16:18:33 | Re: Ghost data from failed FDW transactions? |
Previous Message | Amitabh Kant | 2024-08-28 14:54:41 | Re: PgbackRest : Stanza creation fails on DB Server and Repo Server |