From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Barman versus pgBackRest |
Date: | 2018-09-04 15:51:51 |
Message-ID: | 45526839-10a0-a22e-bde3-6d0a01eeb509@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/4/18 11:24 AM, Joshua D. Drake wrote:
> On 09/04/2018 07:52 AM, Ron wrote:
>> On 09/04/2018 09:24 AM, Joshua D. Drake wrote:
>>> On 09/04/2018 07:14 AM, Ron wrote:
>>>>
>>>> That was about barman, in the barman group. This is asking about
>>>> pgbackrest... :)
>>>>
>>>> So: does pgbackrest have this ability which barman does not have?
>>>> The "--db-include" option seems to indicate that you can restore a
>>>> single db, but does indicate whether or not you can rename it.
>>>
>>> https://pgbackrest.org/configuration.html#section-restore/option-db-include
>>>
>>>
>>
>> Which implies that you can't do it?
>
> You can restore a single database and then issue a simple ALTER DATABASE
> command to change the DB name.
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.
Regards,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2018-09-04 15:55:15 | Re: Barman versus pgBackRest |
Previous Message | Ron | 2018-09-04 15:51:40 | Re: Barman versus pgBackRest |