Re: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: fan(dot)liu(at)ericsson(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
Date: 2020-03-25 11:38:30
Message-ID: 20200325113830.GA25387@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Mar 25, 2020 at 11:11:11AM +0000, PG Bug reporting form wrote:
> eric-adp-ss7-db-pg-0:/var/lib/postgresql/data/pgdata # du -h -d1
> 3.9G ./pg_wal
> 600K ./global
> …..
> 3.9G .
>
> postgres=# SHOW max_wal_size;
> max_wal_size
> --------------
> 1GB
> (1 row)

Please show us:
show archive_mode;
show archive_command;
select * from pg_stat_replication;
select * from pg_replication_slots;
select pg_current_wal_lsn();

and, from postgres account in shell:
ps uwwxf | grep -C3 archive

Best regards,

depesz

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Fan Liu 2020-03-25 11:51:45 RE: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
Previous Message PG Bug reporting form 2020-03-25 11:11:11 BUG #16317: max_wal_size does not remove WAL files, cause "no space left"