Re: zabbix on postgresql - very slow delete of events

From: Kristian Ejvind <Kristian(dot)Ejvind(at)resurs(dot)se>
To: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: zabbix on postgresql - very slow delete of events
Date: 2019-07-23 13:41:53
Message-ID: FECD4549-3F9B-43E5-A475-3996D5E3F22F@resurs.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Thanks Kenneth. In fact we've already partitioned the largest history* and trends* tables
and that has been running fine for a year. Performance was vastly improved. But since you
can't have a unique index on a partitioned table in postgres 10, we haven't worked on that.

Regards
Kristian

?On 2019-07-23, 14:58, "Kenneth Marshall" <ktm(at)rice(dot)edu> wrote:

Hi Kristian,

Time series databases like Zabbix work poorly with the Housekeeper
service. We had many similar sorts of problems as our Zabbix usage
grew. Once we partitioned the big tables, turned off the Housekeeper,
and cleaned up by dropping partitions instead everything worked much,
much, much better. When we started using partitioning, we used the
old inheiritance style. Now you can use the native partitioning.

Regards,
Ken

Resurs Bank AB
Kristian Ejvind
Linux System Administrator
IT Operations | Technical Operations

Ekslingan 8
Box 222 09, SE-25467 Helsingborg

Direkt Tfn:
Mobil: +46 728571483
Vxl: +46 42 382000
Fax:
E-post: Kristian(dot)Ejvind(at)resurs(dot)se
Webb: http://www.resursbank.se

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kenneth Marshall 2019-07-23 14:33:00 Re: zabbix on postgresql - very slow delete of events
Previous Message Kenneth Marshall 2019-07-23 12:58:03 Re: zabbix on postgresql - very slow delete of events