Re: BUG #14340: pg xlog size increasing

From: Vik Fearing <vik(at)2ndquadrant(dot)fr>
To: kgmeetsonu(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14340: pg xlog size increasing
Date: 2016-09-26 14:48:22
Message-ID: 8a3a6780-18f6-d23a-2350-ac7ad335c9e7@2ndquadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 09/26/2016 03:53 PM, kgmeetsonu(at)gmail(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14340
> Logged by: sonu gupta
> Email address: kgmeetsonu(at)gmail(dot)com
> PostgreSQL version: 9.4.9
> Operating system: Red Hat 4.8.5-4, 64-bit
> Description:
>
> Hi,
>
> I created a new DB, with a master and 2 slave nodes on different data
> centers.
>
> I observed, pg xlog size is increasing rapidly and now its 183 GB, while
> simple update is going on on a single table.
>
> xlog size is not getting down...
>
> I assume, missing some config setting.
>
> Please help me, its urgent.
>
> Thanks in advance!!!

This is not a bug, please direct future questions like this to the
pgsql-general list.

Check that your archive_command is functioning correctly, and that you
don't have any inactive replication slots (select * from
pg_replication_slots where not active). Also check the server logs if
both those things are okay.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2016-09-27 02:05:24 WAL senders sending base backups not listening much to SIGTERM
Previous Message Iurii Popov 2016-09-26 14:29:31 Re: BUG #14310: Triggers do not fire