Re: Barman versus pgBackRest
От | David Steele |
---|---|
Тема | Re: Barman versus pgBackRest |
Дата | |
Msg-id | 45526839-10a0-a22e-bde3-6d0a01eeb509@pgmasters.net обсуждение исходный текст |
Ответ на | Re: Barman versus pgBackRest ("Joshua D. Drake" <jd@commandprompt.com>) |
Ответы |
Re: Barman versus pgBackRest
|
Список | 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@pgmasters.net
В списке pgsql-general по дате отправления: