From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Too many WAL archive files
Date: Tue, 23 Jan 2018 06:35:22 -0700 (MST)
Message-ID: <1516714522555-0.post@n3.nabble.com> (raw)
In-Reply-To: <CAJghg4+6yASQfkXYPkeP_wXj5Q9dW+4Ubi=PVtW9sQZgBm5DRQ@mail.gmail.com>
References: <417C5AF7C228B94490192951394BEFE7B3DC00@AIPHLEXDAG01B.airgas.com>
<CAJghg4+6yASQfkXYPkeP_wXj5Q9dW+4Ubi=PVtW9sQZgBm5DRQ@mail.gmail.com>
Hi Matheus de Oliveira,
It is the same case with me too. The archive files are being generated to a
vast extent of 2 GB per hour. And the wal_keep_segments parameter is set 0.
And we are not following any replication practices. The size of the database
is 24GB. Daily 48GB of archive logs are being generated and this abnormal
behaviour started from December 28'th 2017.
The set of DML's which were ran before and after December 28'th 2017 are the
same. So why these many archive logs are being generated? Those are causing
a severe disk space problem.
And FYI autovacuum was set to on. But when I tried doing vacuumdb for this
database almost 1GB of archive logs are getting generated per 1 sec.
It seems to be very strange, any idea of why it is generating?(to prevent
transaction Id wraparound failures? If yes how long it will generate?)
I'm facing this issue from December 28'th 2017. Please suggest how to cope
with it. Thanks in Advance.
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
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: pavan.postgresdba@gmail.com
Subject: Re: Too many WAL archive files
In-Reply-To: <1516714522555-0.post@n3.nabble.com>
* 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