Table of Contents
12 Upgrade notes for 7.0.1
Breaking changes
Server crash with PostgreSQL/TimescaleDB after upgrade from 7.0
Upgrading to Áú»¢¶Ä²© 7.0.1 (or later) from Áú»¢¶Ä²© 7.0.0 with PostgreSQL/TimescaleDB results in a server crash. This issue is caused by a workaround to a compression job issue in the auditlog table in Áú»¢¶Ä²© 7.0 that irreversibly changed the compression policy of the auditlog table.
See known issues for details of fixing the auditlog table manually.
Note that there should be no such issues for upgrades from pre-7.0 Áú»¢¶Ä²© versions to 7.0.1 (or later). For upgrade instructions, see Upgrading TimescaleDB schema.
Database restore error with PostgreSQL/TimescaleDB after upgrade from 7.0.0-7.0.4
Using to restore a PostgreSQL/TimescaleDB backup created in Áú»¢¶Ä²© 7.0.0-7.0.4 will result in a missing base36_decode function error, causing the restore to fail. This error occurs when restoring a backup created with .
See known issues for details on fixing this issue manually before creating the backup.
If you have not upgraded to Áú»¢¶Ä²© 7.0.0 yet, note that there should be no such issues for upgrades from pre-7.0 Áú»¢¶Ä²© versions to 7.0.5. For upgrade instructions, see Upgrading TimescaleDB schema.
Other
New index on auditlog table
A new index has been added to the auditlog table to improve database and frontend response times when filtering records by Recordset ID in the Audit log.
Note that users with large audit logs may experience extended upgrade times due to the database size.
Minimum required TimescaleDB version
The minimum required version of TimescaleDB is now 2.13.0.
Server to stop with read-only database
A standalone Áú»¢¶Ä²© server will now stop if the database becomes read-only.
Items
VMware event log monitoring
The vmware.eventlog item now also returns user information.
DNS service performance
The net.dns.perf item now returns a response time instead of 0 when the DNS server responds with an error code (for example, NXDOMAIN or SERVFAIL).