Re: Standby is not removing restored WAL segments

From: Alexey Klyukin <alexk(at)hintbits(dot)com>
To: Adalkonda Harshad <adalkondaharshad(at)gmail(dot)com>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Standby is not removing restored WAL segments
Date: 2014-09-16 13:03:33
Message-ID: CAAS3tyJ1SEhJSnWs20yW+xVXrvDwhPYMGYmWBA_RSiEu=A=rmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Sep 16, 2014 at 2:20 PM, Adalkonda Harshad
<adalkondaharshad(at)gmail(dot)com> wrote:
>

> I suspect there is a problem while setting the archive_command that resulting towards accumulating WAL .ready file in pg_xlog/archive_status directory itself.

I think archive_command has no effect on the non-primary server, and
the problem described above is happening on standby.
It's hard to suspect the restore_command as well, because the WAL
segments are copied to the pg_xlog as a result of the restore_command,
and therefore, it's working.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jerry Sievers 2014-09-16 17:06:59 Re: log message from autovac doesn't include db name
Previous Message Adalkonda Harshad 2014-09-16 12:20:12 Re: Standby is not removing restored WAL segments