Re: Standby is not removing restored WAL segments

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: Alexey Klyukin <alexk(at)hintbits(dot)com>
Cc: bricklen <bricklen(at)gmail(dot)com>, "pgsql-admin\(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Standby is not removing restored WAL segments
Date: 2014-09-08 17:06:45
Message-ID: 86y4tudot6.fsf@jerry.enova.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Alexey Klyukin <alexk(at)hintbits(dot)com> writes:

> On Mon, Sep 8, 2014 at 3:52 AM, bricklen <bricklen(at)gmail(dot)com> wrote:
>
>>
>> On Fri, Sep 5, 2014 at 12:33 AM, Alexey Klyukin <alexk(at)hintbits(dot)com> wrote:
>>>
>>> We've got a 9.3.5 DB running in a standby mode for a fairly large DB
>>> (500GB) with a busy WAL traffic (couple of GBs per hour) and it
>>> occasionally 'forgets' to remove the segments it restored.
>>
>>
>> A complete shot in the dark, but do you take backups from that server, and
>> if so, does the backup script "pause" replication via
>> "pg_xlog_replay_pause()"? If so, "select pg_is_xlog_replay_paused();" should
>> return true, and executing "select pg_xlog_replay_resume()" will un-pause
>> replication.
>
>
>
>>
>> Again, that's only a WAG.
>>
>
> Thanks. we do take DB backups from this server, but not from this
> cluster on it, so it's not a backup interference.

Or... Are your backups being taken using rsync or any non-pg_basebackup
method *and* you are copying unnecessary WALs to the target new standby
server, which then lay around forever as artifacts of not having been
omitted initially?

>
> --
> Regards,
> Alexey Klyukin

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Eduardo Morras 2014-09-09 08:45:24 Re: Standby is not removing restored WAL segments
Previous Message Scott Marlowe 2014-09-08 16:05:48 Re: Problems with PG 9.3