| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Craig Jackson <craig(dot)jackson(at)broadcom(dot)com>, Don Seiler <don(at)seiler(dot)us> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: High COMMIT times |
| Date: | 2021-01-08 09:05:53 |
| Message-ID: | 21dda7db608a2c454d25e799242948e655965df2.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Tarkeshwar Rao | 2021-01-08 11:59:57 | RE: Autovacuum not functioning for large tables but it is working for few other small tables. |
| Previous Message | Don Seiler | 2021-01-07 18:03:08 | Re: High COMMIT times |