Subject: Re: 8.2 Autovacuum BUG ?
To: pgsql-performance@lists.postgresql.org
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>
 <1516708261537-0.post@n3.nabble.com>
From: Andreas Kretschmer <andreas@a-kretschmer.de>
Message-ID: <be4983c9-ae44-f068-ee02-d4b7e4c8d2bd@a-kretschmer.de>
Date: Tue, 23 Jan 2018 15:17:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <1516708261537-0.post@n3.nabble.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk


Am 23.01.2018 um 12:51 schrieb pavan95:
> 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.

Will so many wals continue to be produced?


>
> 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.
Don't delete wal's!


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

have you set archive_mode to on and defined an archive_command? 
Wal-files will be reused after 2 checkpoints.
Is there something in the logs?


Regards, Andreas
-- 
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com