| 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 14:24:07 |
| Message-ID: | 9c69ec56-d094-e4e7-d7ab-f2ae6652604a@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
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. *****
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2018-09-04 14:52:10 | Re: Barman versus pgBackRest |
| Previous Message | Kumar, Virendra | 2018-09-04 14:18:00 | RE: psqlODBC |