Message-ID: <1510039830.2845.32.camel@cybertec.at>
Subject: Re: Standby wal issue
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: chris kim <chrisk@propaas.com>, pgsql-admin@postgresql.org
Date: Tue, 07 Nov 2017 08:30:30 +0100
In-Reply-To: <2e665cd4-da55-ae82-bdb7-c26e7ba91547@propaas.com>
References: <2e665cd4-da55-ae82-bdb7-c26e7ba91547@propaas.com>
Organization: Cybertec
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

chris kim wrote:
> I have a standby server that is in replication mode only, and is storing 
> an insane amount of wal files and it's only on the standby not the 
> master. I have over 50,000 wal files right now. I only have a few 
> processes running on the background and they all seem to not be the 
> problem. This is running on postgres 9.2. Any help would be greatly 
> appreciated.

Check the "pg_stat_replication" view to see if the standby keeps up
applying the changes - failure to do so could be a reason for WAL piling up.

If host standby is active, is "max_standby_streaming_delay" configured so that
long running transactions on the standby could block replication?

Yours,
Laurenz Albe


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin