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)