The difference is that postgres can enforce this for arbitrary queries.
This doesn't matter in the typical webapp where all accesses to the DB happen through the same database user id, but when actually using the user system of the DB, it allows for fine grained access control to a common data set.
The closest you have without explicit RLS support is to create a view for each user. RLS generates per-user views on demand under a common name.
I am very familiar with RLS, but not schemas. Could you provide an example of how you would use schemas? If not too much trouble, could you also use my salesperson example from my other comments?
This doesn't matter in the typical webapp where all accesses to the DB happen through the same database user id, but when actually using the user system of the DB, it allows for fine grained access control to a common data set.
The closest you have without explicit RLS support is to create a view for each user. RLS generates per-user views on demand under a common name.