From: Laurenz Albe <laurenz.albe@cybertec.at>
To: chris kim <chrisk@propaas.com>
To: pgsql-admin@postgresql.org
Subject: Re: Standby wal issue
Date: Tue, 07 Nov 2017 08:30:30 +0100
Message-ID: <1510039830.2845.32.camel@cybertec.at> (raw)
In-Reply-To: <2e665cd4-da55-ae82-bdb7-c26e7ba91547@propaas.com>
References: <2e665cd4-da55-ae82-bdb7-c26e7ba91547@propaas.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, chrisk@propaas.com
Subject: Re: Standby wal issue
In-Reply-To: <1510039830.2845.32.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox