From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | postgresdba12(at)outlook(dot)com |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Postgres Wal Full |
Date: | 2022-03-03 08:22:15 |
Message-ID: | 20220303.172215.717210688663246493.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At Thu, 3 Mar 2022 07:46:45 +0000, pgdba pgdba <postgresdba12(at)outlook(dot)com> wrote in
> I have a problem from pg_wal. I am using postgresql version 11 and taking backup and writing archive_command in postgresql.conf but did not archive wal and my disk ise full from pg_wal. I research why is my wal is full and dont found anything could you help me please ?
The immediate cause of the WAL retension is the archive failure.
PostgreSQL, while archiving is enabled, won't remove a WAL file until
it is successfully archived.
You will see the lines like the following in sergver log if archive
failure happened.
> 2022-03-03 17:15:21.314 JST LOG: archive command failed with exit code 1
If the archive command emitted some error messages, it can be caught
in the server log together. The follwoing error is emitted by the
archive_command "cp %p /archive/%f".
> cp: cannot create regular file '/archive/000000010000000000000001': No such file or directory
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | pgdba pgdba | 2022-03-03 08:47:20 | Ynt: Postgres Wal Full |
Previous Message | Andreas Kretschmer | 2022-03-03 08:04:37 | Re: Postgres Wal Full |