Re: [Maria-discuss] 10.2.7 and xtradb in changelog
Am 13.07.2017 um 11:55 schrieb Sergei Golubchik:
On Jul 13, Reindl Harald wrote:
https://mariadb.com/kb/en/mariadb/mariadb-1027-changelog/
i
I don't find this extremely confusing (if it's a change to the code, it's not weird to see it in the changelog; filtering out things exposes us to bugs in the filtering process, which may hide important information) but I think that there is another confusing part. In this page:
https://mariadb.com/kb/en/mariadb/why-does-mariadb-102-use-innodb-instead-of...
I read:
"Note, we still consider incorporating XtraDB optimizations, but as patches, rather than XtraDB as a whole"
But then, it is not clear what exactly is or is not in MariaDB's InnoDB. Percona has a nice list of features:
https://www.percona.com/doc/percona-server/LATEST/index.html
It would be useful to have a list of which changes are applied to MariaDB's InnoDB. Hope it is not too hard to maintain.
Cheers,
Federico
--------------------------------------------
Gio 13/7/17, Sergei Golubchik
is it back now with
commits with no context to the version of the release?
Neither. Changelog is generated as "all commits that are present in the 10.2.7 history, but were not present in the 10.2.6 history". And all
commits in 10.1 are merged into 10.2 eventually (because many 10.1
bugfixes apply to 10.2 too).
So whatever was done to XtraDB in 10.1 it will be part of 10.2 revision
history, even though XtraDB itself is disabled in 10.2 (and does not
even compile
I agree that it's confusing, but what can we do? Manually filter out all
commits
10.2.7 or is the changelog a random wild mix of there). that contain the string "xtradb" from the changelog?
well,
at least some filters make sense because things like "Update
xtradb and innodb version to 5.6.36" are pure nonsense when innodb in 10.2 AFAIK is 5.7 and so the complete changelog feels very useless and
instead beeing helpful it spreads doubt how that whole stuff works at
all when random pieces seems to get merged bewteen versions or at least the changelog says so
Okay. https://jira.mariadb.org/browse/MDEV-13312 Regards, Sergei Chief Architect MariaDB and security@mariadb.org _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
Am 13.07.2017 um 13:17 schrieb Federico Razzoli:
I don't find this extremely confusing (if it's a change to the code, it's not weird to see it in the changelog; filtering out things exposes us to bugs in the filtering process, which may hide important information)
frankly with such a big change like 10.2 it is not confusing but a no-go that the maned server don't start at all instead just log no longer supported options
Hi, regarding changelog I have a bit more problem for example with this issue MDEV-12992 ( https://jira.mariadb.org/browse/MDEV-12992 ) which bassically makes 10.2.6 unusable for production (most likely a DB will have a trigger or two and sooner or later you'll hit OOM). I was trying to find it in the 10.2.7 changelog (nearly got to the point of writing an email to mailinglist) but found it after doublechecking just the number - for some reason it doesn't follow the typical description (like MDEV-[number] Bug title/description) rather than hardly noticable: "Revision #7a12894de1 2017-06-10 16:39:39 -0700 Fixed the bug mdev12992. " wbr rr
I think this is another result of changelogs being maintaned automatically
(as Harald already noticed). Changelogs is MariaDB are hardly usable unless
you are deeply involved in the coding yourself. Unlike MySQL/Oracle be
where you may actually be e4nriched by skim-reading changelogs for new
releases.
-- Peter
On Thu, Jul 13, 2017 at 3:27 PM, Reinis Rozitis
Hi, regarding changelog I have a bit more problem for example with this issue MDEV-12992 ( https://jira.mariadb.org/browse/MDEV-12992 ) which bassically makes 10.2.6 unusable for production (most likely a DB will have a trigger or two and sooner or later you'll hit OOM).
I was trying to find it in the 10.2.7 changelog (nearly got to the point of writing an email to mailinglist) but found it after doublechecking just the number - for some reason it doesn't follow the typical description (like MDEV-[number] Bug title/description) rather than hardly noticable:
"Revision #7a12894de1 2017-06-10 16:39:39 -0700 Fixed the bug mdev12992. "
wbr rr
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
participants (4)
-
Federico Razzoli -
Peter Laursen -
Reindl Harald -
Reinis Rozitis