| 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 10:06:17 |
| Message-ID: | FF569708-B596-469F-981F-B5C7A6AD3AA5@aol.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
>
> Not , am saying we have the daily backup and full backup in prod server only and there is one database like a4 the db size is 1.5TB.
> so am not restore again in prod .
> Am taking directly single backup restore in dev its means in dev server only restore the database in new cluster.
> existing cluster we cant restore backups.
> so thats why am struggling the issue getting some perl issue and remote option terminated otherwise wont disturb anyone and need to solve this issue.
> this activity has been planned every 3 weeks.
>
Sorry I am not able to follow the above. Did anyone else ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2019-05-14 13:06:54 | Re: perl path issue |
| Previous Message | Prakash Ramakrishnan | 2019-05-14 09:51:58 | Re: perl path issue |