From: | <soumik(dot)bhattacharjee(at)kpn(dot)com> |
---|---|
To: | <pgsql-admin(at)lists(dot)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | FW: Database Locks , Performance Issues and How to Resolve? |
Date: | 2019-12-30 15:40:18 |
Message-ID: | 2A91BEF8171A5349931391E0C721CC537D775496@CPEMS-KPN501.KPNCNL.LOCAL |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sorry resending the mail, as my mail server bounced.
Please ignore if already received.
Thanks..
From: Bhattacharjee, Soumik
Sent: maandag 30 december 2019 16:09
To: pgsql-admin(at)lists(dot)postgresql(dot)org; pgsql-admin(at)postgresql(dot)org
Subject: Database Locks , Performance Issues and How to Resolve?
Hi Experts,
In our TEST database - PostgreSQL 10 - We are facing issue while executing SELECT queries from application concurrently.
Select statements taking long some time (almost ½ hr) and it goes into lock mode even after we have COMMIT in the updates.
In PGADMIN dashboard, database applied exclusive lock on table cfs.next_nm_tabl.
This issue is major for us, and huge performance issue for applications.
Attached the spreadsheet with all details of LOCKS.
Please suggest how to handle this in PostgreSQL , as this never is an issue when we simulate the same in Oracle?
Query from application:
2019-12-28 20:00:17.185 DEBUG 25032 --- [pool-2-thread-1] org.hibernate.SQL :
update
cfs.next_nm_tabl
set
next_nm=?
where
nm_typ_ind=?
DB Locks details from PGADMIN:
[cid:image006(dot)jpg(at)01D5BEF7(dot)21BCD280]
Attachment | Content-Type | Size |
---|---|---|
data-1577680020226_dev.xls | application/vnd.ms-excel | 32.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | soumik.bhattacharjee | 2019-12-30 15:54:54 | RE: Database Locks , Performance Issues and How to Resolve? |
Previous Message | soumik.bhattacharjee | 2019-12-30 15:09:23 | Database Locks , Performance Issues and How to Resolve? |