Sorry Kristian, I do not know where I came up with "54". We are running 10.5.27.
Respectfully, Mark MARK S. ELLENBERGER, CTR, PERATON, INC. DATABASE ENGINEERING, ADVISOR IT Capabilities Contract II -----Original Message----- From: Kristian Nielsen <[email protected]> Sent: Thursday, 18 September, 2025 16:28 To: mark.s.ellenberger.ctr--- via discuss <[email protected]> Cc: Ellenberger, Mark Steven CTR STRATCOM J64 (USA) <[email protected]> Subject: Re: [MariaDB discuss] "PURGE BINARY LOGS" not deleting logs; no errors "mark.s.ellenberger.ctr--- via discuss" <[email protected]> writes: > I am running 10.5.34 Community Version and I am trying to set up my 10.5.34? That version doesn't seem to exist? > test environment running "PURGE BINARY LOGS BEFORE 'YYYY-MM-DD > hh:mm:ss'" the command works but when I run it in my production > environment it does not delete anything. There are no errors returned The usual source of confusion here is the variable slave_connections_needed_for_purge, which was introduced with a default value of 1. This means that by default, no binlog files can be purged if no slave is connected. This variable was introduced in 11.4.1. You can try to `SET GLOBAL slave_connections_needed_for_purge=1` and see if it helps. > I am at a loss! At this point the only thing I know to do is to add a > "rm" command to remove logs and a "sed" command to update the .index > file to the end of my backup script but I really do not want to do > that. No, that should not be needed. - Kristian.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
