pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Balashov <abalashov@evaristesys.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: pg_wal keeps growing
Date: Wed, 3 Feb 2021 11:00:17 -0500
Message-ID: <BCAE1B1C-D694-4CE3-9EEF-ED610BD3F9B1@evaristesys.com> (raw)
In-Reply-To: <CALhHtcCBE2mSLp3XWr659ga-KE8_YDh9YGD9jJ0NBD8TBy1RpA@mail.gmail.com>
References: <CALhHtcCBE2mSLp3XWr659ga-KE8_YDh9YGD9jJ0NBD8TBy1RpA@mail.gmail.com>

Are you sure you don’t have a replication slot with no replication consumer connected to it?

Replication slots cause WALs to accumulate until someone connects to the slot and downloads them.

—
Sent from my iPad

> On Feb 3, 2021, at 10:53 AM, Yambu <hyambu@gmail.com> wrote:
> 
> 
> Hello
> 
> My pg_wal directory keeps growing in size. Im using Pg v10
> 
> Currently its at 53GB in size.
> 
> Below are my settings
> 
>  select name,setting,unit from pg_settings where name ilike '%wal%';
>              name             |  setting  | unit
> ------------------------------+-----------+------
>  max_wal_senders              | 10        |
>  max_wal_size                 | 1024      | MB
>  min_wal_size                 | 80        | MB
>  wal_block_size               | 8192      |
>  wal_buffers                  | 2048      | 8kB
>  wal_compression              | off       |
>  wal_consistency_checking     |           |
>  wal_keep_segments            | 0         |
>  wal_level                    | replica   |
>  wal_log_hints                | off       |
>  wal_receiver_status_interval | 10        | s
>  wal_receiver_timeout         | 60000     | ms
>  wal_retrieve_retry_interval  | 5000      | ms
>  wal_segment_size             | 2048      | 8kB
>  wal_sender_timeout           | 60000     | ms
>  wal_sync_method              | fdatasync |
>  wal_writer_delay             | 200       | ms
>  wal_writer_flush_after       | 128       | 8kB
> (18 rows)





view thread (5+ messages)  latest in thread

Message-ID: <BCAE1B1C-D694-4CE3-9EEF-ED610BD3F9B1@evaristesys.com>
Permalink:  ../BCAE1B1C-D694-4CE3-9EEF-ED610BD3F9B1@evaristesys.com/
Also on:    postgresql.org/message-id/BCAE1B1C-D694-4CE3-9EEF-ED610BD3F9B1@evaristesys.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: abalashov@evaristesys.com, pgsql-admin@lists.postgresql.org
  Subject: Re: pg_wal keeps growing
  In-Reply-To: <BCAE1B1C-D694-4CE3-9EEF-ED610BD3F9B1@evaristesys.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox