A Postgres production database experienced high CPU usage due to an inefficiently written Row-Level Security policy that repeatedly parsed JWT tokens for every row accessed. The issue went undetected by standard debugging tools because the privileged role used for testing bypassed RLS evaluation, masking the actual query cost. Rewriting the policy to evaluate the JWT function once per statement rather than per row reduced peak CPU from 80% to 16%.