liveBook · Manning

Row-level security

Row-level security is a database access-control technique that restricts users’ access to table rows according to policies or predicates.

How 2 Manning books explain it

Architecting an Apache Iceberg Lakehouse

A row-level filter restricts access to records according to predicates applied at query or policy evaluation time.

How it is used
Enforces governed record access across BI tools, embedded analytics, APIs, and other consumption paths.
How deep it goes
Explains architectural placement and deployment scenarios but does not provide policy syntax or detailed predicate implementation.
Examples
Uses a governed global bank and a multi-tenant e-commerce dashboard as concrete deployment examples.
What you can do after
Apply it via query engines, federation layers, BI tools, and APIs to isolate records for authorized users or tenants.

Read how Architecting an Apache Iceberg Lakehouse explains row-level security →

PostgreSQL Mistakes and How to Avoid Them

Row-level security is a database access-control mechanism that restricts which table rows individual users can access.

How it is used
Restricts which table rows users can access while exposing risks from privileged object ownership.
How deep it goes
Explains RLS bypass through superuser-owned views and points to security_barrier protection without detailing policy syntax.
Examples
Uses an unprivileged user querying a superuser-owned view and receiving rows despite RLS restrictions.
What you can do after
Diagnose unexpected row exposure by checking view ownership and considering security_barrier protection.

Read how PostgreSQL Mistakes and How to Avoid Them explains row-level security →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.