Zabbix/partitioning
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: COMMITs added to release locks immediately. UTC usage. Testing env for test branch.

Browse Source
This commit is contained in:
Maksym Buz
2026-02-19 21:53:51 +00:00
parent 8565c99310
commit c4420bc1ad
29 changed files with 864923 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
postgresql/procedures/README.md
View File

@@ -2,7 +2,13 @@
This is the declarative (PostgreSQL procedures based) partitioning implementation for Zabbix `history`, `trends`, and `auditlog` tables on PostgreSQL. This solution is intended to replace standard Zabbix housekeeping for the configured tables. Partitioning is very useful for large environments because it completely eliminates the housekeeper from the process. Instead of huge DELETE queries on several million rows, fast DDL queries (ALTER TABLE) are executed, which drop an entire partition.
## Architecture
4:
5: > [!CRITICAL]
6: > **High-Load Environments**:
7: > 1. **Data Visibility**: After enabling partitioning, old data remains in `*_old` tables and is **NOT visible** in Zabbix. You must migrate data manually if needed.
8: > 2. **Disable Housekeeping**: You **MUST** disable Zabbix Housekeeper for History and Trends in *Administration -> General -> Housekeeping*. Failure to do so will cause massive `DELETE` loads.
9:
10: ## Architecture
The solution uses PostgreSQL native declarative partitioning (`PARTITION BY RANGE`).
All procedures, information, statistics and configuration are stored in the `partitions` schema to maintain full separation from Zabbix schema.