| From: | José Arthur Benetasso Villanova <jose(dot)arthur(at)gmail(dot)com> |
|---|---|
| To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: High COMMIT times |
| Date: | 2021-01-08 17:51:55 |
| Message-ID: | CA+soXCPwygP4ezA+-D6Nfc2WA1KWhAPYzcVUk_hNuPapK3nSLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jan 7, 2021 at 3:03 PM Don Seiler <don(at)seiler(dot)us> wrote:
> On Thu, Jan 7, 2021 at 11:50 AM Craig Jackson <craig(dot)jackson(at)broadcom(dot)com>
> 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.
>>
>
> Interesting, I'll run a check for any. Thanks!
>
> Don.
>
> --
> Don Seiler
> www.seiler.us
>
Do you have standby databases and synchronous_commit = 'remote_apply'?
--
José Arthur Benetasso Villanova
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2021-01-08 19:04:30 | Re: High COMMIT times |
| Previous Message | Michael Lewis | 2021-01-08 15:52:36 | Re: Autovacuum not functioning for large tables but it is working for few other small tables. |