pg_xlog on slaves has grown to 200GB

From: Vikas Sharma <shavikas(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: pg_xlog on slaves has grown to 200GB
Date: 2019-08-20 14:17:21
Message-ID: CAN6gwKydz6mid68EKVgU7WMJcRG4mv=RACeJmyJVA=AKoyV3nw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

We are using postgresql 9.5 with repmgr 3.3.2 in streaming replication
setup with 1 master and 2 slaves. I have noticed that the pg_xlog on slaves
has grown to 200GB and is still growing.

Please advise why pg_xlog is growing and not pruning itself, is there any
parameter I need to setup to accomplish this? or repmgr will control it
itself.

I am not 100% sure but feel it pg_xlog never used to grow this much or was
clearing itself, I can see there are WALs since May 2019 but not before
that. I want to understand why the WALs started accumulating since then. we
have this setup since more than a year.

Best Regards
Vikas Sharma

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2019-08-20 14:19:39 Re: postmaster utilization
Previous Message Tom Lane 2019-08-20 14:02:07 Re: pg_dump problems: [archiver (db)] query failed: ERROR: relation "pg_opfamily" does not exist