Re: 8.2 Autovacuum BUG ?

From: Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org, Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>
Subject: Re: 8.2 Autovacuum BUG ?
Date: 2018-01-23 16:16:11
Message-ID: CACh9nsYX23u1eLngVx2j5_0CBhUH=MJN9HE6iYOSgNrk5gfnFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Jan 23, 2018 9:37 PM, "Claudio Freire" <klaussfreire(at)gmail(dot)com> wrote:

On Tue, Jan 23, 2018 at 11:39 AM, Pavan Teja <pavan(dot)postgresdba(at)gmail(dot)com>
wrote:

> Yes so many wals are continuing to be produced.
>
> Deleting the wals after a backup of the database.
>
> Yes archiving mode is on. And the warning message in log file is
>
> " checkpoints are frequently occurring (1second apart). Consider
> increasing checkpoint_segements parameter".
>
> My doubt is previously the same are the parameters which are reflected as
> of now. Then what is the point in considering altering those values.
> Correct me if I am wrong.
>

You can use pg_xlogdump to inspect those logs and see which
relations/transactions are generating so much WAL.

Then you can hunt within your apps which code is responsible for that
traffic, or whether it in fact is autovacuum.

Hi Claudio,

Is pg_xlogdump available for postgres 9.1, as my current production is
postgres 9.1.

Yes investigated in that area, found DML's and also autovacuum statements
for some relations. And the DML's are the same before this huge WAL traffic
and normal WAL traffic.

Anyways, thanks for your timely response 😊

Regards,
Pavan

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Matthew Bellew 2018-01-23 17:18:51 Re: Bad plan
Previous Message Claudio Freire 2018-01-23 16:07:34 Re: 8.2 Autovacuum BUG ?