| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, "Ahmed, Nawaz" <Nawaz(at)fast(dot)au(dot)fujitsu(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Barman disaster recovery solution |
| Date: | 2019-02-28 08:40:30 |
| Message-ID: | 68c955ea-70e1-3143-106f-f504ed9efb13@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/28/19 9:21 AM, Achilleas Mantzios wrote:
> On 28/2/19 1:08 π.μ., Ahmed, Nawaz wrote:
>>
>> Hi,
>>
>> I believe the "file copy" method (listed in the table) in pgbackrest
>> is based on pg_basebackup, so i think it should be "pg_basebackup over
>> ssh" as pgbackrest internally calls pg_basebackup. David Steele can
>> correct me.
>>
> No, apparently pgbackrest does not rely on pg_basebackup.
pgBackRest implements file copy internally and does not rely on any
command-line tools such as rsync, tar, pg_basebackup, etc.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-02-28 09:29:03 | Re: Overloaded && operator from intarray module prevents index usage. |
| Previous Message | Thomas Kellerer | 2019-02-28 07:47:11 | Overloaded && operator from intarray module prevents index usage. |