Re: BUG #16317: max_wal_size does not remove WAL files, cause "nospace left" - Mailing list pgsql-bugs

From hubert depesz lubaczewski
Subject Re: BUG #16317: max_wal_size does not remove WAL files, cause "nospace left"
Date
Msg-id 20200325113830.GA25387@depesz.com
Whole thread Raw
In response to BUG #16317: max_wal_size does not remove WAL files, cause "no space left"  (PG Bug reporting form <noreply@postgresql.org>)
Responses RE: BUG #16317: max_wal_size does not remove WAL files, cause "nospace left"  (Fan Liu <fan.liu@ericsson.com>)
List 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




pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
Next
From: Fan Liu
Date:
Subject: RE: BUG #16317: max_wal_size does not remove WAL files, cause "nospace left"