From: Kenneth Marshall <ktm@rice.edu>
To: Kristian Ejvind <Kristian.Ejvind@resurs.se>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: zabbix on postgresql - very slow delete of events
Date: Tue, 23 Jul 2019 09:33:00 -0500
Message-ID: <20190723143300.GG21184@aart.rice.edu> (raw)
In-Reply-To: <FECD4549-3F9B-43E5-A475-3996D5E3F22F@resurs.se>
References: <3EC00A37-57CF-4B43-A737-968A87B02641@contoso.com>
<20190723125803.GD21184@aart.rice.edu>
<FECD4549-3F9B-43E5-A475-3996D5E3F22F@resurs.se>
On Tue, Jul 23, 2019 at 01:41:53PM +0000, Kristian Ejvind wrote:
> 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
Hi Kristian,
Why are you not partitioning the events and alerts tables as well? That
would eliminate this problem and you already have the infrastructure in
place to support the management since you are using it for the history
and trends tables.
Regards,
Ken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ktm@rice.edu, Kristian.Ejvind@resurs.se, pgsql-performance@lists.postgresql.org
Subject: Re: zabbix on postgresql - very slow delete of events
In-Reply-To: <20190723143300.GG21184@aart.rice.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox