Wodenokoto may have different explanation, but I'm guessing it's just down to the raw data processed. If you're making a view that winds up running a query on t

Wodenokoto may have different explanation, but I'm guessing it's just down to the raw data processed. If you're making a view that winds up running a query on the origin table with a `WHERE` added, then you're still processing the entire table for each query. I don't think row-level security will be any better based on this documentation.