From 9d1b84225c8a1a54bdff778ecd88999b7bf43b9f Mon Sep 17 00:00:00 2001 From: Maksym Buz Date: Fri, 20 Feb 2026 18:57:45 +0000 Subject: [PATCH] docs: Change admonition type from critical to warning in README.md --- postgresql/procedures/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/postgresql/procedures/README.md b/postgresql/procedures/README.md index 466dd8c..0a554ef 100644 --- a/postgresql/procedures/README.md +++ b/postgresql/procedures/README.md @@ -3,7 +3,7 @@ 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. -> [!CRITICAL] +> [!WARNING] > **High-Load Environments**: > 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. > 2. **Disable Housekeeping**: You **MUST** disable Zabbix Housekeeper for History and Trends in *Administration -> Housekeeping*. Failure to do so will cause massive `DELETE` loads.