From: Pepe TD Vo <pepevo@yahoo.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Subject: Re: slave stops replica
Date: Fri, 27 Aug 2021 10:56:01 +0000 (UTC)
Message-ID: <1948635055.176990.1630061761986@mail.yahoo.com> (raw)
In-Reply-To: <1e79ea171debe2b3ed9c297989f110cfccdf129b.camel@cybertec.at>
References: <1415172523.18991.1630012160409.ref@mail.yahoo.com>
<1415172523.18991.1630012160409@mail.yahoo.com>
<1e79ea171debe2b3ed9c297989f110cfccdf129b.camel@cybertec.at>
Can we delete the old WALs? May I know what is the retention to perform tuning on the server like Oracle to keep only 7 days and why pg_archivecleanup doesn't work?
Bach-Nga
On Friday, August 27, 2021, 03:29:54 AM EDT, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Thu, 2021-08-26 at 21:09 +0000, Pepe TD Vo wrote:
> I had master slave replica and yesterday the slave server's device was full on /var
> where the archive copy from master. After trying to figure out why the
> pg_archivecleanup doesn't work, SA removed all wal files except the current
>
> I tried to create a test table on master and didn't see it pick up from slave.
> I found out again /var is full.
If you have deleted WAL that has no yet been applied to the standby, replication
is broken and you have to build the standby from scratch.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pepevo@yahoo.com, pgsql-admin@lists.postgresql.org, laurenz.albe@cybertec.at
Subject: Re: slave stops replica
In-Reply-To: <1948635055.176990.1630061761986@mail.yahoo.com>
* 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