Date: Tue, 23 Jan 2018 04:51:01 -0700 (MST)
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-performance@postgresql.org
Message-ID: <1516708261537-0.post@n3.nabble.com>
In-Reply-To: <97fd02a3-c07c-6d27-6221-b50c2c8c13cc@a-kretschmer.de>
References: <46D83427.60001@livedatagroup.com>
 <1516601350338-0.post@n3.nabble.com> <987851516614060@web46o.yandex.ru>
 <1516616499481-0.post@n3.nabble.com>
 <97fd02a3-c07c-6d27-6221-b50c2c8c13cc@a-kretschmer.de>
Subject: Re: 8.2 Autovacuum BUG ?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Andreas,

Yes I'm facing problem because of this huge WAL(archive log) generation. As
it is seriously consuming a lot of disk space almost close to 50GB per day
even if the DML's don't have that impact in this WAL generation.

Previously the archive_log size is nearly 2 to 3 GB a day. Now with the same
set of DML's how is it being generated to 50GB is my burning doubt.

I just wanted to know how to stabilize this issue, as checking and deleting
the archive logs on hourly basis is not a good idea.

Finally, I'm looking how to reduce this back to normal. Thanks in Advance.

Regards,
Pavan  


--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html