| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Barman versus pgBackRest |
| Date: | 2018-09-04 15:55:15 |
| Message-ID: | 5dc5b1df-053a-3d61-e5e5-338de15d771e@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-09-04 16:00:59 | Re: Barman versus pgBackRest |
| Previous Message | David Steele | 2018-09-04 15:51:51 | Re: Barman versus pgBackRest |