Re: Standby problem after restore_command Implementation

From: Venkata Balaji N <nag1010(at)gmail(dot)com>
To: "Edson F(dot) Lidorio" <edson(at)openmailbox(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Standby problem after restore_command Implementation
Date: 2015-05-05 22:49:22
Message-ID: CAEyp7J_OqMF5io477BwHEX_c6YDKbUvoN31hk5RgMY49zp8nwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, May 5, 2015 at 7:57 AM, Edson F. Lidorio <edson(at)openmailbox(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Kehlet 2015-05-06 01:40:33 finding tables about to be vacuum freezed
Previous Message Adrian Klaver 2015-05-05 22:09:47 Re: Standby problem after restore_command Implementation