Re: Barman versus pgBackRest - Mailing list pgsql-general

From Ron
Subject Re: Barman versus pgBackRest
Date
Msg-id 5dc5b1df-053a-3d61-e5e5-338de15d771e@gmail.com
Whole thread Raw
In response to Re: Barman versus pgBackRest  (David Steele <david@pgmasters.net>)
Responses Re: Barman versus pgBackRest  (David Steele <david@pgmasters.net>)
Re: Barman versus pgBackRest  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
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?

-- 
Angular momentum makes the world go 'round.


pgsql-general by date:

Previous
From: David Steele
Date:
Subject: Re: Barman versus pgBackRest
Next
From: David Steele
Date:
Subject: Re: Barman versus pgBackRest