| From: | Ravi Krishna <ravi_krishna(at)aol(dot)com> |
|---|---|
| To: | Prakash Ramakrishnan <prakash(dot)ramakrishnan(dot)ap(at)nielsen(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, David Steele <david(at)pgmasters(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: perl path issue |
| Date: | 2019-05-14 09:40:41 |
| Message-ID: | 6888C5C1-CB5A-41DD-976F-466E298CCBD6@aol.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> Note - if am taking same prod single database backup and restore in new cluster no use for us and it will take more time.
> so business and team they need every 3 weeks for restore in dev server one single database and cant we do it in pg_dump and restore .
> They want using pgbackrest tool the db size is huge so tats why am trying remote restore option.
I am baffled. Are you telling that you are restoring it back on prod (using remote restore option),
which effectively means overwriting prod db. Also you never gave this information until now. You
should have shared full details.
I have not used pgbackest, but I have read the FAQ. If I am not mistaken it has single db restore option too. So you can restore
the db in dev.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prakash Ramakrishnan | 2019-05-14 09:51:58 | Re: perl path issue |
| Previous Message | Prakash Ramakrishnan | 2019-05-14 08:21:08 | Re: perl path issue |