| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: postgres complete recovery |
| Date: | 2019-04-22 22:19:55 |
| Message-ID: | CAKFQuwb-HYedY9r2NKZWkCswEA5wuTOYPPX=EoDj6k=1VqxVTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Apr 22, 2019 at 3:02 PM Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> wrote:
> Hello David,
>
> Thank you so much for clarification.
> is there any way to keep redundant copy of current wall log on same
> server? means, as soon as transaction commits, it it going to make an entry
> in wal log and the same log in different location ?
> please advise
>
PostgreSQL itself will only write to a single file. It may be possible to
setup an operating system tool (like inotifywait) to accomplish this but
its not something I've tried or seen discussed or recommended in my reading.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AYahorau | 2019-04-23 06:47:35 | A special tool for PostgreSQL which checks its operability |
| Previous Message | Pavan Kumar | 2019-04-22 22:01:54 | Re: postgres complete recovery |