From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Craig Jackson <craig.jackson@broadcom.com>
To: Don Seiler <don@seiler.us>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: High COMMIT times
Date: Fri, 08 Jan 2021 10:05:53 +0100
Message-ID: <21dda7db608a2c454d25e799242948e655965df2.camel@cybertec.at> (raw)
In-Reply-To: <CA+R1LV5F_ngEkJDQOZ=mKHU80km0h3B-ybXzh-g2C=3HZ6ju3g@mail.gmail.com>
References: <CAHJZqBCsS5wiUemiArXMXR4Oo63_9bBfssrXWieE7X55dYEvNw@mail.gmail.com>
<CA+R1LV5F_ngEkJDQOZ=mKHU80km0h3B-ybXzh-g2C=3HZ6ju3g@mail.gmail.com>
On Thu, 2021-01-07 at 10:49 -0700, Craig Jackson wrote:
> We had a similar situation recently and saw high commit times that were caused
> by having unindexed foreign key columns when deleting data with large tables involved.
> You might check to see if any new foreign key constraints have been added
> recently or if any foreign key indexes may have inadvertently been removed.
> Indexing the foreign keys resolved our issue.
Were these deferred foreign key constraints?
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
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: laurenz.albe@cybertec.at, craig.jackson@broadcom.com, don@seiler.us, pgsql-performance@lists.postgresql.org
Subject: Re: High COMMIT times
In-Reply-To: <21dda7db608a2c454d25e799242948e655965df2.camel@cybertec.at>
* 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