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>
 <be4983c9-ae44-f068-ee02-d4b7e4c8d2bd@a-kretschmer.de>
 <CACh9nsb76gbS0LabzpoDUCB86ORVF765p-Y3BeF3sT2VLnE3cw@mail.gmail.com>
 <CACh9nsZNe=BefOeuq5w9C-rTBLaTPQPYWqXBW7aKN9J+HEijxQ@mail.gmail.com>
 <CACh9nsa7vmMoNUnu8T9-rXJ21HtaKDXpqUr+pyPPuzXwLmu8vg@mail.gmail.com>
 <CACh9nsYLe8qQNHb4tdEi1e13tVCoGht_vrSViemGBgNhYHy9+w@mail.gmail.com>
 <CACh9nsbvTBeh322cLKgFLCajOkDRC7zULMFZ7xBcE5UhoR6wgQ@mail.gmail.com>
 <CACh9nsYnQMDsOniYk-NLX+zOqKy-5P3VSBpv3msFy7_B8wx-xg@mail.gmail.com>
 <CACh9nsb5dF6wNC=iyaxGyrHZ212QkbtXtO36it9u-QhOFr6j2g@mail.gmail.com>
 <CAKFQuwaPT1VuD1UyyHAOhk=nWj2mHUmHgz2XZtXKfwcVpXqGvQ@mail.gmail.com>
 <CACh9nsb8RqkRrtUwfS9CooPAJComUWCJ6A_EeAdVirHKH5JGtA@mail.gmail.com>
From: Andreas Kretschmer <andreas@a-kretschmer.de>
Message-ID: <20fdd406-eef8-7fab-f3eb-9203bbfb8c10@a-kretschmer.de>
Date: Tue, 23 Jan 2018 16:26:44 +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: 
 <CACh9nsb8RqkRrtUwfS9CooPAJComUWCJ6A_EeAdVirHKH5JGtA@mail.gmail.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 16:20 schrieb Pavan Teja:
> Hi David,
>
> If it's yes what needs to be done in order to stabilize this issue??
>

Don't top-post ;-)


You can't prevent the generation of wal's (apart from using unlogged 
tables, but i'm sure, that will be not your solution.)

Regards, Andreas

-- 
2ndQuadrant - The PostgreSQL Support Company.
www.2ndQuadrant.com