How an inefficient Row-Level Security policy drove Postgres CPU to 80%; and why EXPLAIN failed to reveal it.
1 comment
prasadvara2 days ago
I feel that when we opt for row level security we are fundamentally moving away from CRUD principles and maybe not a good candidate in RDS. I have used this approach lock the rows from UI modifications, but felt like awkward way of restricting.
Read the full thread on Hacker News →
Related stories
- Simple and Efficient Row-Level Securityacadia.engineeringHacker News · 1 points · 10 days ago
- Hacker News · 1 points · 3 days ago
- Forging 1024-bit RSA signatures in nearly SNFS timeeprint.iacr.orgLobsters · 7 points · 6 days ago
- Hacker News · 119 points · about 7 hours ago
- Ars Technica · 0 points · 9 days ago
- On Improvements of Low-Deterministic Security (2016)pp.ipd.kit.eduLobsters · 2 points · about 8 years ago