Partitioning

[JanCZ]

Hello i ran into issue - how to easily partition postgres database to prevent index overgrowth in our database, for Zabbix 3.4+. We have currently older version of Zabbix using following script (bit outdated, but working up till 3.2)

http://www.zabbix.org/wiki/Docs/howto/zabbix2_postgresql_autopartitioning

Also i found alternative script directly for version 3.2

https://github.com/cavaliercoder/zabbix-pgsql-partitioning

But non of them is apparently compatible with Zabbix 3.4+. Not even mentioning we may postpone clean reinstall until Zabbix 4.0 LTS. I would like to know if somebody can help with this issue, to identify it at least. There is still option to stick with 3.2.2 but i would like to prevent it and to go at least for 3.4 and in the best case scenario right for 4.0 (since we are aiming for clean reinstall anyway)
Any advice/idea/opinion is very welcome for discussion.

Thank you

[JanCZ]

So mabye my question was not properly asked, in the mean time i found some new info:

Did anyone successfully implemented new Postgres 10 native partitioning feature to work with Zabbix lets say 3.2 - 3.4 ?? Iam looking for example case or mabye some tutorial - zabbix wiki is sadly not helpful with this.

Thank you

[doctorbal82]

Hello JanCZ,

I wrote about using PostgreSQL 10 Native Range Partitioning on the clock column here - https://www.zabbix.com/forum/zabbix-...for-zabbix-3-4.

Ensure you create Indexes! I made the mistake in the script and updated it.

Also PostgreSQL 11 will have automagic Index creation. Some new features of PSQL 11 are mentioned here - https://pgdash.io/blog/partition-postgres-11.html.

I would test on a DEV environment as much as possible.