ZBXNEXT-2941 is distantly related.

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-3135

(1)
This is first time, after 3.0, 2.4 and 2.2, when we will perform changes on historical tables.
The very last "heavy" change which I can recall was added nanoseconds in 2.0.

So, maybe worth to specially mention on whatsnew32 page that upgrade may take more time than previous major upgrades because a few historical tables are involved.

• What's new in 3.2.0
• Upgrade notes for 3.2.0

wiper CLOSED

Server side was successfully tested with minor change in r58319. Please take a look.

wiper Thanks, reviewed

(2) API and frontend

sasha RESOLVED in r58320

iivs CLOSED

zalex, very good idea in (1) - but probably in upgrade notes. in whatsnew the performance improvement + slight db size reduction could be mentioned

(3) No translation string changes.

wiper CLOSED

API and Frontend TESTED

Released in:

• pre-3.1.0 58602

This resulted in new warnings:

[...]
Making install in zbxdbupgrade
dbupgrade_2010.c: In function ‘DBpatch_2010101’:
dbupgrade_2010.c:946:5: warning: implicit declaration of function ‘quote_key_param’ [-Wimplicit-function-declaration]
     quote_key_param(&param, 0);
     ^
dbupgrade_2010.c: In function ‘replace_key_param’:
dbupgrade_2010.c:1664:2: warning: implicit declaration of function ‘unquote_key_param’ [-Wimplicit-function-declaration]
  unquote_key_param(param);
  ^

The cause (sysinfo.h removed from includes):

$ svn diff -c58602 src/libs/zbxdbupgrade/dbupgrade_2010.c
Index: src/libs/zbxdbupgrade/dbupgrade_2010.c
===================================================================
--- src/libs/zbxdbupgrade/dbupgrade_2010.c      (revision 58601)
+++ src/libs/zbxdbupgrade/dbupgrade_2010.c      (revision 58602)
@@ -19,10 +19,8 @@
 
 #include "common.h"
 #include "db.h"
-#include "log.h"
-#include "sysinfo.h"
-#include "zbxdbupgrade.h"
 #include "dbupgrade.h"
+#include "log.h"
 
 /*
  * 2.2 development database patches

sasha fixed directly in trunk r59021. CLOSED

There was idea that database upgrade would be faster if we'd leave the id fields in base, just dropping primary key and updating field to allow nulls. However tests on mysql database (default settings) showed that it would take twice the time needed to drop id fields.

please reopen for minor documentation updates - looks like (1) was closed without a review

• trailing dot missing here : https://www.zabbix.com/documentation/3.2/manual/installation/upgrade_notes_320#database_upgrade
• in https://www.zabbix.com/documentation/3.2/manual/introduction/whatsnew320 , it does not say what benefit removing those fields provides

wiper added dot, more comments.