How an inefficient Row-Level Security policy drove Postgres CPU to 80%; and why EXPLAIN failed to reveal it.

2 points•bucket2015•2 days ago•1 comment•

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