| From: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org, pgsql-in-general(at)postgresql(dot)org, Christoph Berg <myon(at)debian(dot)org>, Koichi Suzuki <koichi(dot)dbms(at)gmail(dot)com>, Koichi Suzuki <koichidbms(at)gmail(dot)com> |
| Subject: | Soluton on Lock:extend issue |
| Date: | 2024-08-10 16:52:39 |
| Message-ID: | CAJCZkoKUW18gbPu00W4WHXsBDM+7GvPiah1s-W+gKV41DpYbDw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-in-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2024-08-10 17:15:46 | Re: Soluton on Lock:extend issue |
| Previous Message | Adrian Klaver | 2024-08-10 14:52:31 | Re: Insert works but fails for merge |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2024-08-10 17:15:46 | Re: Soluton on Lock:extend issue |
| Previous Message | Muhammad Imtiaz | 2024-07-30 11:22:17 | Re: Scheduling pg_repack job with pg_cron |