Re: Barman versus pgBackRest

Поиск
Список
Период
Сортировка
Искать
От
David Steele
Тема
Re: Barman versus pgBackRest
Дата
Msg-id
a4da7752-363e-4bae-c12b-2631694c137b@pgmasters.net
Ответ на
Список
Дерево обсуждения
Barman versus pgBackRest Thomas Poty <thomas.poty@gmail.com>
Re: Barman versus pgBackRest David Steele <david@pgmasters.net>
Re: Barman versus pgBackRest Achilleas Mantzios <achill@matrix.gatewaynet.com>
Re: Barman versus pgBackRest "Jehan-Guillaume (ioguix) de Rorthais" <ioguix@free.fr>
Re: Barman versus pgBackRest Achilleas Mantzios <achill@matrix.gatewaynet.com>
Re: Barman versus pgBackRest Thomas Poty <thomas.poty@gmail.com>
Re: Barman versus pgBackRest David Steele <david@pgmasters.net>
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@pgmasters.net

В списке pgsql-general по дате отправления
От: Ron
Дата:
Сообщение: Re: Barman versus pgBackRest
От: Joshua D. Drake
Дата:
Сообщение: Re: Barman versus pgBackRest
FAQ