Re: Barman versus pgBackRest

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
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:01:52
Message-ID: 2454adca-c4b6-39c7-80f0-a435404b0209@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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. *****

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Steele 2018-09-04 16:29:48 Re: Barman versus pgBackRest
Previous Message David Steele 2018-09-04 16:00:59 Re: Barman versus pgBackRest