Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marco Boeringa <marco(at)boeringa(dot)demon(dot)nl>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Fwd: "SELECT COUNT(*) FROM" still causing issues (deadlock) in PostgreSQL 14.3/4?
Date: 2022-07-23 15:33:55
Message-ID: 883945.1658590435@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Marco Boeringa <marco(at)boeringa(dot)demon(dot)nl> writes:
> Ok, I found it out using 'sudo baobab'. It is the:
> 'var/lib/postgresql/14/main/pg_wal'

> folder that is filled up with 890 GB of data... causing the file system
> root to run out of space and Ubuntu opening the disk usage analyzer and
> a warning as a consequence.

The most likely explanations for this are
(a) misconfiguration of WAL archiving, so that the server thinks
it should keep WAL files till they've been archived, only that
never happens.
(b) inability to complete checkpoints for some reason, preventing
WAL files from being recycled.

It doesn't look like you have wal_archiving on, so (a) *should*
be ruled out, but you never know. If there are a ton of "nnn.ready"
files underneath pg_wal then trouble here would be indicated.

As for (b), you might try enabling log_checkpoints and seeing if
the log messages give any clue.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Zsolt Ero 2022-07-23 16:39:55 Re: could not link file in wal restore lines
Previous Message Japin Li 2022-07-23 14:33:46 Re: BUG #17557: ts_headline will error with "invalid memory alloc request size" for large documents