pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: fan.liu@ericsson.com
Subject: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
Date: Wed, 25 Mar 2020 11:11:11 +0000
Message-ID: <16317-b7ad5f27ad90aceb@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16317
Logged by:          Fan Liu
Email address:      fan.liu@ericsson.com
PostgreSQL version: 10.10
Operating system:   suse
Description:        

Hello,

We are working on PostgreSQL 10.10. We recently met “no space left”.
After checking, the WAL file folder is full. There is no heavy traffic.
But we have wal_max_size = 1G configured. I am not that understand why this
can happen. 
Is this a BUG? 

=== LOG ===
## /var/lib/postgresql/data is a network storage with 4G space

pg-0:/var/lib/postgresql/data/pgdata/pg_wal # ls -alh
total 3.9G
drwx------  3 postgres postgres  20K Mar 21 02:31 .
drwx------ 19 postgres postgres 4.0K Mar 21 02:31 ..
-rw-------  1 postgres postgres  16M Feb 20 14:05

eric-adp-ss7-db-pg-0:/var/lib/postgresql/data/pgdata # du -h -d1
3.9G    ./pg_wal
600K    ./global
…..
3.9G    .

cat postgresql.conf
# Do not edit this file manually!
# It will be overwritten by Patroni!
include 'postgresql.base.conf'

cluster_name = 'ss7-db-pg'
hot_standby = 'on'
listen_addresses = '*'
logging_collector = 'off'
max_connections = '100'
max_locks_per_transaction = '64'
max_prepared_transactions = '0'
max_replication_slots = '10'
max_wal_senders = '10'
max_worker_processes = '8'
port = '5432'
track_commit_timestamp = 'off'
wal_keep_segments = '8'
wal_level = 'replica'
wal_log_hints = 'on'
hba_file = '/var/lib/postgresql/data/pgdata/pg_hba.conf'
ident_file = '/var/lib/postgresql/data/pgdata/pg_ident.conf'

postgres=# SHOW max_wal_size;
max_wal_size
--------------
1GB
(1 row)

BRs,
Fan Liu



view thread (7+ messages)  latest in thread

Message-ID: <16317-b7ad5f27ad90aceb@postgresql.org>
Permalink:  ../16317-b7ad5f27ad90aceb@postgresql.org/
Also on:    postgresql.org/message-id/16317-b7ad5f27ad90aceb@postgresql.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: noreply@postgresql.org, fan.liu@ericsson.com
  Subject: Re: BUG #16317: max_wal_size does not remove WAL files, cause "no space left"
  In-Reply-To: <16317-b7ad5f27ad90aceb@postgresql.org>
  References: <16317-b7ad5f27ad90aceb@postgresql.org>

* 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