Timeline for PostgreSQL triggered update function lock mechanism
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2022 at 7:22 | comment | added | Damien | When I inspect that table it’s not always there, but during a load testing (thousands of requests per second) I can see some locks every few tries. Thanks for the help I’ll take a look at that extension. | |
| May 28, 2022 at 15:28 | comment | added | Laurenz Albe |
There must have been an additional row lock, but row locks are not stored in the lock table for very long. You could use the pgrowlocks extension to find out more.
|
|
| May 28, 2022 at 13:10 | comment | added | Damien | Thank you fot he answer, indeed after looking at pg_locks there's some RowExclusiveLock. So from what I understand that kind of lock is a table lock, but it locks only a single row based on an id just like we do when using an advisory lock ? | |
| May 28, 2022 at 13:07 | vote | accept | Damien | ||
| May 27, 2022 at 17:53 | history | answered | Laurenz Albe | CC BY-SA 4.0 |