Re: Standby problem after restore_command Implementation - Mailing list pgsql-general

From Venkata Balaji N
Subject Re: Standby problem after restore_command Implementation
Date
Msg-id CAEyp7J_OqMF5io477BwHEX_c6YDKbUvoN31hk5RgMY49zp8nwg@mail.gmail.com
Whole thread Raw
In response to Standby problem after restore_command Implementation  ("Edson F. Lidorio" <edson@openmailbox.org>)
List pgsql-general

On Tue, May 5, 2015 at 7:57 AM, Edson F. Lidorio <edson@openmailbox.org> wrote:


On 04-05-2015 00:46, Venkata Balaji N wrote:
You do not see the above WAL file in the archive directory ? "/mnt/server/archivedir" is shared between master and slave databases ? The file may have been removed from the archive location.
Strange !!
Yes, this specified folder file "/ mnt / server / ArchiveDir".
At this shared folder between master and slave.

I suspect that archive cleanup job is cleaning up the archives. "archive_cleanup_command" removes any archives not needed for recovery.

Since the the archive destination is shared across master and slave. Archives are removed and Standby is not getting the required archives.

To avoid this, before you do any tests, i suggest remove "archive_cleanup_command" parameter and see if you are still facing the same problem.

Regards,
Venkata Balaji N

Fujitsu Australia

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Standby problem after restore_command Implementation
Next
From: Steve Kehlet
Date:
Subject: finding tables about to be vacuum freezed