RC1s of 27.0.1, 26.0.4 and 25.0.9

Maintenance releases of 27.0.1, 26.0.4 and 25.0.9 are coming next Thursday and RCs for those are now available on our download server.

As always, help with testing is very much welcome!

We updated our servers, did our tests, and the release candidates seem pretty decent. Still, give it a whirl and report back here so we’re even more sure that it’s good to go! If you notice anything out of order, please report back on the appropriate github repository! :bowing_woman:

Downloads

Changelog

27.0.1rc1

26.0.4rc1

25.0.9rc1

2 Likes

Looks like missing index “systag_by_tagid” in table “oc_systemtag_object_mapping” does not get created by
occ db:add-missing-indices

EDIT:

The /settings/admin/overview throws this message:

but:

MariaDB [nextcloud]> DESCRIBE oc_systemtag_object_mapping;
+-------------+---------------------+------+-----+---------+-------+
| Field       | Type                | Null | Key | Default | Extra |
+-------------+---------------------+------+-----+---------+-------+
| objectid    | varchar(64)         | NO   | PRI |         |       |
| objecttype  | varchar(64)         | NO   | PRI |         |       |
| systemtagid | bigint(20) unsigned | NO   | PRI | 0       |       |
+-------------+---------------------+------+-----+---------+-------+
3 rows in set (0.001 sec)

MariaDB [nextcloud]> SHOW INDEXES FROM oc_systemtag_object_mapping;
+-----------------------------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| Table                       | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | Index_comment |
+-----------------------------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
| oc_systemtag_object_mapping |          0 | PRIMARY  |            1 | objecttype  | A         |           2 |     NULL | NULL   |      | BTREE      |         |               |
| oc_systemtag_object_mapping |          0 | PRIMARY  |            2 | objectid    | A         |      143547 |     NULL | NULL   |      | BTREE      |         |               |
| oc_systemtag_object_mapping |          0 | PRIMARY  |            3 | systemtagid | A         |      143547 |     NULL | NULL   |      | BTREE      |         |               |
+-----------------------------+------------+----------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+
3 rows in set (0.001 sec)

See here: fix(systemtags): Add missing systemtags index by marcelklehr · Pull Request #38928 · nextcloud/server · GitHub

I can confirm this issue. After running occ db:add-missing-indices it still complains about missing indexes.

Thank you for reporting! Fix in fix(db): no hardcoded table prefix is expected by blizzz · Pull Request #39380 · nextcloud/server · GitHub

2 Likes

Thanks! Works.

But:

occ db:add-missing-indices --dry-run

did not work, at least not for this operation:

~# occ db:add-missing-indices --dry-run
Check indices of the share table.
Check indices of the filecache table.
Check indices of the twofactor_providers table.
Check indices of the login_flow_v2 table.
Check indices of the whats_new table.
Check indices of the cards table.
Check indices of the cards_properties table.
Check indices of the calendarobjects_props table.
Check indices of the schedulingobjects table.
Check indices of the oc_properties table.
Check indices of the oc_jobs table.
Check indices of the oc_direct_edit table.
Check indices of the oc_preferences table.
Check indices of the oc_mounts table.
Check indices of the oc_systemtag_object_mapping table.
Adding systag_by_tagid index to the oc_systemtag_object_mapping table, this can take some time...
oc_systemtag_object_mapping table updated successfully.

Hope this helps-

For the record, and as some might have seen on Github, this is also a valid finding, but not specific to this added index alone, and will be treated in an upcoming release.

2 Likes