Open byte opened 8 months ago
Is it enough to add: Deprecated as of Galera Cluster 4.00/MySQL-wsrep 8.0 or do we need more detailed versions?
I would go for a bit more detail (e.g. Galera 4 / MySQL-wsrep with a version. It is also worth noting that the versions that it did support, are now no longer in production use cases... i.e. they have all reached EOL status (even 5.7 that is published now is considered to be the last release, maybe there's another if upstream does so, but it is more or less done for).
Which is the first MySQL-wsrep version where this was deprecated? 8.0.19-26.3?
8.0.19-26.3-beta3
Thank you
On Tue, Feb 13, 2024 at 5:13 PM Kirjaamo Information < @.***> wrote:
Which is the first MySQL-wsrep version where this was deprecated?
— Reply to this email directly, view it on GitHub https://github.com/codership/documentation/issues/402#issuecomment-1940689652, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAO5CYZ4KWWQSXSSO7LWFDYTMOCBAVCNFSM6AAAAABBOEOL56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBQGY4DSNRVGI . You are receiving this because you authored the thread.Message ID: @.***>
via @sciascid in mysql 8/galera 4 the variable defaults now to 'optimized', whereas in 5.7 the default value was 'strict'. Also, in 8.0, changing the value of variable has no effect
this means that it is deprecated
https://galeracluster.com/library/documentation/mysql-wsrep-options.html#wsrep-certification-rules
(for reference, this was released in sep 2018 as a new feature - https://galeracluster.com/2018/09/releasing-galera-cluster-3-24-with-improved-deadlock-error-management/)