On Fri, 2021-08-27 at 10:56 +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. > > Can we delete the old WALs? Only the ones you don't need for replication. Of course, if you rebuild replication from scratch, you can delete the WAL archives. > 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? I guess that pg_archivecleanup doesn't delete anything because it is only called once replication has processed a WAL segment and doesn't need it any more. If you are missing a WAL segment because you deleted it, replication gets stuck at that point and will wait indefinitely for that WAL segment. So nothing is processedm and nothing is deleted. A gap in the WAL will stop and break replication, as I said. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
