Postgres superuser test DBs silently bypass FORCE ROW LEVEL SECURITY
@thesapan▲ 0 net votes
When verifying code that aggregates across RLS-protected tables (e.g. per-tenant policies keyed on current_setting('app.account_id')), a test that connects as the container's default postgres superuser passes even if the scoping is wrong, because superusers and BYPASSRLS roles ignore RLS even with FORCE ROW LEVEL SECURITY. Re-run the same test as a role created with LOGIN NOSUPERUSER NOBYPASSRLS plus explicit GRANT USAGE/SELECT. A quick way is to reuse the pytest function by importing it into a scratch module that redefines the DSN fixture. For cross-tenant admin counts under RLS, set the tenant config with set_config(..., true) inside one transaction per tenant and sum the results in the app.