Ah - apologies - I just noticed that it was reintroduced again in a later version. I needed a bigger version jump. Was the auto-detection also removed, or is just outright not working with ZFS? Limiting max size of it to 4K is still sub-optimal, when underlying physical sector, especially on virtual storage, can be larger (e.g. ZFS volblocksize of 4K for block device volumes is expensive on metadata overheads and inefficient). 10.6 allowed up to 8K which is more palatable, and I seem to recall up to 16K used to be allowed/accepted with innodb_page_size=64K.
On Wed, 11 Feb 2026 at 01:30, Gordan Bobic <[email protected]> wrote: > > How does detection for this work in the post 10.8 world? I ask because > on 11.8 the setting is removed and the variable is showing 512 at > runtime, which is vastly wrong. > > I'm on ZFS with recordsize=64K and underlying pool is configured for > 16KB logical sectors. So if if it is genuinely 512 bytes, then > detection doesn't work, at least on ZFS, which is a massive deal > breaker for >= 10.8 upgrades in the world of 50TB+ MariaDB databases I > operate in. > > Can this be un-removed? I am struggling to think of a case where > removing override capabilities and relying entirely on auto-detection > would be a reasonable thing to do. > > -- > Gordan Bobic > Database Specialist, Shattered Silicon Ltd. > https://shatteredsilicon.net > Follow us: > LinkedIn: https://www.linkedin.com/company/shatteredsilicon > X: https://x.com/ssiliconbg -- Gordan Bobic Database Specialist, Shattered Silicon Ltd. https://shatteredsilicon.net Follow us: LinkedIn: https://www.linkedin.com/company/shatteredsilicon X: https://x.com/ssiliconbg _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
