Re: Standby is not removing restored WAL segments - Mailing list pgsql-admin

From Alexey Klyukin
Subject Re: Standby is not removing restored WAL segments
Date
Msg-id CAAS3tyJ1SEhJSnWs20yW+xVXrvDwhPYMGYmWBA_RSiEu=A=rmw@mail.gmail.com
Whole thread Raw
In response to Standby is not removing restored WAL segments  (Alexey Klyukin <alexk@hintbits.com>)
Responses Re: Standby is not removing restored WAL segments  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-admin
On Tue, Sep 16, 2014 at 2:20 PM, Adalkonda Harshad
<adalkondaharshad@gmail.com> wrote:
>

> I suspect there is a problem while setting the archive_command that resulting towards accumulating WAL .ready file in
pg_xlog/archive_statusdirectory 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.


pgsql-admin by date:

Previous
From: Alexey Klyukin
Date:
Subject: Re: Standby is not removing restored WAL segments
Next
From: Jerry Sievers
Date:
Subject: Re: log message from autovac doesn't include db name