MIME-Version: 1.0
From: Durgamahesh Manne <maheshpostgres9@gmail.com>
Date: Sat, 10 Aug 2024 22:22:39 +0530
Message-ID: <CAJCZkoKUW18gbPu00W4WHXsBDM+7GvPiah1s-W+gKV41DpYbDw@mail.gmail.com>
Subject: Soluton on Lock:extend issue
To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org, 
	Christoph Berg <myon@debian.org>, Koichi Suzuki <koichi.dbms@gmail.com>, 
	Koichi Suzuki <koichidbms@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000006dcc69061f57102e"
Archived-At: <https://www.postgresql.org/message-id/CAJCZkoKUW18gbPu00W4WHXsBDM%2B7GvPiah1s-W%2BgKV41DpYbDw%40mail.gmail.com>
Precedence: bulk

--0000000000006dcc69061f57102e
Content-Type: text/plain; charset="UTF-8"

Hi

Lock:extend  (version 14.11)
How to resolve lock:extend issue even there is surge in concurrent sessions
(insert and update) on same table

Reduction on concurrent sessions would be solved but that is not a solution
and
there is no network bandwidth issue

Is there any parameter to tune to minimize the impact on lock:extend ?

Regards,
Durga Mahesh

--0000000000006dcc69061f57102e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi=C2=A0=C2=A0<div><br></div><div>Lock:extend=C2=A0 (versi=
on 14.11)</div><div>How to resolve=C2=A0lock:extend issue even there is sur=
ge in concurrent sessions (insert and update) on same table=C2=A0</div><div=
><br></div><div>Reduction on concurrent sessions would be solved=C2=A0but t=
hat is not a solution and=C2=A0</div><div>there is no network bandwidth iss=
ue=C2=A0</div><div><br></div><div>Is there any parameter to tune to minimiz=
e the impact on lock:extend ?</div><div><br></div><div>Regards,</div><div>D=
urga Mahesh=C2=A0</div></div>

--0000000000006dcc69061f57102e--