From: | Dimitrios Apostolou <jimis(at)gmx(dot)net> |
---|---|
To: | Sergey Fukanchik <fukanchik(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Orphan files filling root partition after crash |
Date: | 2024-02-28 12:51:31 |
Message-ID: | 07f2e362-24a2-f382-decb-c90025ce2d87@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Sergey,
On Wed, 28 Feb 2024, Sergey Fukanchik wrote:
> Hi Dimitrios,
> Do you have wal archiving enabled?
> $PGDATA/pg_wal/ is a bit different from tablespaces (including
> "default" one). It stores transaction journal.
I don't think I have WAL archiving enabled. Here are the relevant WAL
options in my config:
wal_compression = zstd
max_wal_size = 8GB
min_wal_size = 1GB
track_wal_io_timing = on
wal_writer_flush_after = 8MB
The issue happens because the WAL directory is by default in the same
filesystem with the default tablespace (root partition for Ubuntu). So
when the default tablespace filled up because of my ALTER TABLE operation,
there was no space for WAL either.
Thanks,
Dimitris
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Olarte | 2024-02-28 12:53:31 | Re: PostgreSQL Read-only mode usage |
Previous Message | Andreas Joseph Krogh | 2024-02-28 12:37:22 | Sv: PostgreSQL Read-only mode usage |