Re: Postgres Wal Full

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: pgdba pgdba <postgresdba12(at)outlook(dot)com>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres Wal Full
Date: 2022-03-03 09:50:25
Message-ID: CALj2ACXRzT8i++Vb_hJFwa--+y6uFD43OAzZoEHxRQTZWOFvFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Mar 3, 2022 at 2:17 PM pgdba pgdba <postgresdba12(at)outlook(dot)com> wrote:
>
> Hi, thanks your feedback but not have same error in my log file. I am using streaming replication and have 1 master and 2 slave nodes in async. master node different size file wal from slave nodes such as;
> [root(at)master1 pg_wal]# ls | wc -l
> 6400
> [root(at)slave2 pg_wal]# ls | wc -l
> 332
> [root(at)slave3 pg_wal]# ls | wc -l
> 344
>
> wal_keep_segments = 512
> max_wal_size = 2GB
> min_wal_size = 1GB
> data size : 290G
> cpu:8
> ram:16

Few things to check when WAL file grows: 1) archive failures 2)
inactive replication slots (use select * from pg_replication_slots;)
3) infrequent checkpoints (use select * from pg_control_checkpoint; to
know the last checkpoint time)4) high write (WAL-generating)
workloads.

Regards,
Bharath Rupireddy.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Suresh Kumar R 2022-03-03 10:02:27 Couldn't cast to record[]
Previous Message pgdba pgdba 2022-03-03 08:47:20 Ynt: Postgres Wal Full