Re: transaction blocking on COMMIT

From: Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com>
To: Bob Jolliffe <bobjolliffe(at)gmail(dot)com>
Cc: "pgsql-performa(dot)" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: transaction blocking on COMMIT
Date: 2021-05-24 11:35:32
Message-ID: CAM+6J97zHKPOv+5VgBnMyGLWSn5xCFMoUMEstLMtumYWmhVLig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I think there have been similar issues reported earlier as well. But it
would be too early to generalize.

Where is the db server running? Cloud?

Also what is the version ?

On Mon, May 24, 2021, 5:00 PM Bob Jolliffe <bobjolliffe(at)gmail(dot)com> wrote:

> I am seeing a strange issue on a database using jdbc. Regularly, 4 or
> 5 times a day, I see something like a "stutter", where a bundle of
> maybe 30 transactions suddenly finish at the same time. It looks like
> (it is quite hard to catch this exactly) that the lead transaction
> which has been blocking the rest has been blocked in COMMIT. In each
> case it blocks for almost exactly 30s, just over, and once it goes
> through, releases locks, and the others clear behind it.
>
> My question: what are the range of possibilities that might cause a
> COMMIT to block? I haven't seen this before. Is there anything
> suspicious about the regular 30s? Occasionally we see 60s, which
> seems likely to be two sets of 30.
>
> Regards
> Bob
>
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Philip Lykke Carlsen 2021-05-24 12:10:24 Optimising outer joins in the presence of non-nullable references
Previous Message Bob Jolliffe 2021-05-24 11:30:19 transaction blocking on COMMIT