Steve Shaw <steve.shaw@hammerdb.com> writes:

One follow-up question, with the new build if I set log_bin=1 (or skip-log-bin=0) I get the following:

2025-05-16 15:17:43 0 [ERROR] Binlog name can not be set with --log-bin when --binlog-storage-engine is used. Use --binlog-directory to specify a separate directory for binlogs

Sorry, as I wrote originally, you have to use in the config file: log_bin (without any argument). I also missed the detail that you put the "=1" in there, since it looks so natural. (The reason is historical. In the existing server, --log-bin takes the basename to use for the binlog files, it's not an on/off switch. So log_bin=1 means to call the binlog files "1.000001", "1.000002", ... In the new binlog I removed the ability to specify the basename, hence the error rather than silently ignoring the user's specified name).

How do I check its working as intended rather than not having enabled the binlog.

When the new binlog is enabled, the data directory (or --binlog-directory if specified) will contain binlog files named like this: binlog-000000.ibb binlog-000001.ibb ... - Kristian.