Zabbix upgrade to 6.0.11 fails with Postgresql 13.

[sripley]

Greetings, I'm attempting to upgrade our Zabbix 6.0.9 instance and it failed on upgrade to 6.0.11.

The Zabbix server is running OracleLinux 8 with Postgresql 13. All previous upgrades from 5.0.x -> 6.0.9 have worked fine so I'm not sure what happened here.

418791:20221212:173429.956 Zabbix Server stopped. Zabbix 6.0.10 (revision e35d7dceead).
419084:20221212:173515.664 Starting Zabbix Server. Zabbix 6.0.11 (revision 17788cd2098).
419084:20221212:173515.665 ****** Enabled features ******
419084:20221212:173515.665 SNMP monitoring: YES
419084:20221212:173515.665 IPMI monitoring: YES
419084:20221212:173515.665 Web monitoring: YES
419084:20221212:173515.665 VMware monitoring: YES
419084:20221212:173515.666 SMTP authentication: YES
419084:20221212:173515.666 ODBC: YES
419084:20221212:173515.666 SSH support: YES
419084:20221212:173515.666 IPv6 support: YES
419084:20221212:173515.667 TLS support: YES
419084:20221212:173515.667 ******************************
419084:20221212:173515.667 using configuration file: /etc/zabbix/zabbix_server.conf
419084:20221212:173515.818 current database version (mandatory/optional): 06000000/06000007
419084:20221212:173515.819 required mandatory version: 06000000
419084:20221212:173515.819 optional patches were found
419084:20221212:173515.819 starting automatic database upgrade
419084:20221212:173515.851 completed 10% of database upgrade
419084:20221212:173515.881 completed 20% of database upgrade
419084:20221212:173516.017 completed 30% of database upgrade
419084:20221212:173516.123 completed 40% of database upgrade
419084:20221212:173516.126 completed 50% of database upgrade
419084:20221212:173516.133 completed 60% of database upgrade
419084:20221212:173516.488 completed 70% of database upgrade
419084:20221212:173517.560 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: table tid from new index tuple (1029,6) overlaps with invalid duplicate tuple at offset 22 of block 145 in index "items_8"
[update items set name_upper=upper(name)]

[sripley]

I was able to get the upgrade to complete by manually running the sql statements from the stock 6.0.12 sql file used to create a new database. I then started zabbix-server again:

800873:20221216:170726.875 current database version (mandatory/optional): 06000000/06000014
800873:20221216:170726.876 required mandatory version: 06000000
800873:20221216:170726.877 optional patches were found
800873:20221216:170726.877 starting automatic database upgrade
800873:20221216:170726.880 items_name_upper_update trigger for table "items" already exists, skipping patch of updating "name_upper" column
800873:20221216:170726.882 completed 33% of database upgrade
800873:20221216:170726.884 items_name_upper_insert trigger for table "items" already exists, skipping patch of adding it to "items" table
800873:20221216:170726.886 completed 66% of database upgrade
800873:20221216:170726.887 items_name_upper_update trigger for table "items" already exists, skipping patch of adding it to "items" table
800873:20221216:170726.889 completed 100% of database upgrade
800873:20221216:170726.890 database upgrade fully completed

I'm not sure if I need to do anything else to confirm that the upgrade worked or that all the relevant schema changes for 6.0.12 were applied. I assume they were since the database upgrade completed successfully.