| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Bob Jolliffe <bobjolliffe(at)gmail(dot)com> |
| Cc: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>, "pgsql-performa(dot)" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: transaction blocking on COMMIT |
| Date: | 2021-05-24 16:24:09 |
| Message-ID: | 9EED60F9-BD32-4529-B1A0-6AD7F26916B4@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> On May 24, 2021, at 09:22, Bob Jolliffe <bobjolliffe(at)gmail(dot)com> wrote:
>
> It is hard to say as it only happens for 30s couple of times per day.
> Everything does return to normal after the blocking transaction is
> committed. It could be a disk thing or even a network issue (the java
> app is on a different machine to the db). But I never saw
> transactions blocked in commit before so was wondering if there is any
> rational set of reasons why it might do that.
One thing you can check is to turn off synchronous_commit (understanding the possibility of "time loss" in the event of a system crash). If that mitigates the problem, the issue is likely the I/O subsystem blocking during the fsync() operation.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey M Boltenkov | 2021-05-24 21:59:11 | Re: transaction blocking on COMMIT |
| Previous Message | Bob Jolliffe | 2021-05-24 16:22:28 | Re: transaction blocking on COMMIT |