Currently it is possible to set up Zabbix to use TimescaleDB and enable compression, but not select an override for trends or history.
According to documentation:

If using TimescaleDB, in order to take full advantage of TimescaleDB automatic partitioning of history and trends tables, Override item history period and Override item trend period options must be enabled as well as Enable internal housekeeping option for history and trends. Otherwise, the data kept in these tables will still be stored in partitions, however, the housekeeper will be cleaning the history and trends by deleting individual records rather than by dropping outdated partitions. When dropping of outdated partitions is enabled, Zabbix server and frontend will no longer keep track of deleted items and history for deleted items will be cleared when an outdated partition is deleted.

https://www.zabbix.com/documentation/current/manual/web_interface/frontend_sections/administration/general

This can lead to a situation where compression is enabled (and chunks read only) but housekeeper still tries to delete something from there:

5658:20211115:125542.665 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  cannot update/delete rows from chunk "_hyper_3_2099_chunk" as it is compressed
 [delete from history_uint where itemid=XXXX

We should only allow compression to be selected if overrides have been selected for trends and history. In addition not allow un-selecting them if compression is enabled.