3 ms·
Interesting. I did not know that. I have to dig into the source code then. Do you know any alternate logging tools that don't have this issue?
by kvaranasi_ 3y ago
Interesting. I did not know that. I have to dig into the source code then. Do you know any alternate logging tools that don't have this issue?
- vermon 3y agoI think pgAudit it still the best and it's not a major issue. You can try my PR that fixes this issue https://github.com/pgaudit/pgaudit/pull/219 https://github.com/pgaudit/pgaudit/pull/219 it should work and it should handle the other types of SELECT's that need update permissions but are not actually updating anything https://pglocks.org/?pglock=RowShareLock https://pglocks.org/?pglock=RowShareLock
- kvaranasi_ 3y agoOk, looking into it.
- danpalmer 3y agoFYI, be careful, see my other comments in reply but I think this is working correctly, and due to the fact that a `SELECT ... FOR UPDATE` is a write.
- kvaranasi_ 3y agoYes, I have been reading the conversation. That was so much to learn. I did not know that `SELECT ... FOR UPDATE` is "sort of" a write. I googled and found out this SO link: https://stackoverflow.com/questions/18879584/postgres-select-for-update-in-functions https://stackoverflow.com/questions/18879584/postgres-select... that corroborates what you have said.