From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Barman versus pgBackRest |
Date: | 2018-09-04 16:00:59 |
Message-ID: | a4da7752-363e-4bae-c12b-2631694c137b@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/4/18 11:55 AM, Ron wrote:
> On 09/04/2018 10:51 AM, David Steele wrote:
> [snip]
>> This will work, but I don't think it's what Ron is getting at.
>>
>> To be clear, it is not possible to restore a database into an *existing*
>> cluster using pgBackRest selective restore. This is a limitation of
>> PostgreSQL file-level backups.
>>
>> To do what Ron wants you would need to restore it to a new cluster, then
>> use pg_dump to logically dump and restore it to whatever cluster you
>> want it in. This still saves time since there is less to restore but is
>> obviously not ideal.
>
> That's exactly what I'm referring to.
>
> Presumably I could restore it to a new cluster on the same VM via initdb
> on a different port and PGDATA directory?
Definitely. No need to initdb since all the required files will be
restored by pgBackRest. You'll just need to create an empty directory
to restore into.
Regards,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2018-09-04 16:01:52 | Re: Barman versus pgBackRest |
Previous Message | Ron | 2018-09-04 15:55:15 | Re: Barman versus pgBackRest |