Guideline To Resolve LWLock:SubtransControlLock

From: Fred Habash <fmhabash(at)gmail(dot)com>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Guideline To Resolve LWLock:SubtransControlLock
Date: 2018-08-16 18:19:11
Message-ID: CADpeV5wA_Ekz9yNEMKbazwvm+jfhk02tQGjK=G+_4BcGF-2GOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

One of our database API's is run concurrently by near 40 sessions. We see
all of them waiting back and forth on this wait state.

There is one scenario described in some forum where sessions connected a
read-only replica are affected. This does not apply to our use case.

Why is it called Subtrans Control Lock?
What are the common user session scenarios causing this wait?
- I have read some describe the use of SQL savepoints or PL/pgSQL
exception handling.
What are known resolution measures?

----------------------------------------
Thank you

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alvaro Herrera 2018-08-16 18:36:32 Re: Guideline To Resolve LWLock:SubtransControlLock
Previous Message Thomas Munro 2018-08-15 22:42:25 Re: dsa_allocate() faliure