...@postgresql.org
Cc: Wong, Kam Fook (TR Technology)
Subject: Postgres Locking
***ATTENTION!! This message originated from outside of Circana. Treat
hyperlinks and attachments in this email with caution.***
Relatively new to Postgres. Running into a locking situation and I need to
make sure I understand
"Dirschel, Steve" writes:
> Above I can see PID 3740 is blocking PID 3707. The PK on table
> wln_mart.ee_fact is ee_fact_id. I assume PID 3740 has updated a row
> (but not committed it yet) that PID 3707 is also trying to update.
Hmm. We can see that 3707 is waiting for 3740 to commit, because
60/259887 | 3740 | RowExclusiveLock | t
| t|
(25 rows)
I believe the locktype relation is pointing to the table and the indexes on the
table. Which data point(s) above point to this being row-level locking and not
some other level of locking? I am very familiar with Or
