Re: Barman versus pgBackRest - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: Barman versus pgBackRest
Date
Msg-id 2454adca-c4b6-39c7-80f0-a435404b0209@commandprompt.com
Whole thread Raw
In response to Re: Barman versus pgBackRest  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general
On 09/04/2018 08: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?

Yes.

jD


-- 
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
***  A fault and talent of mine is to tell it exactly how it is.  ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
*****     Unless otherwise stated, opinions are my own.   *****



pgsql-general by date:

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