News for hackers. Stuff that matters.
Re:Scaling to 1M active GraphQL subscriptions on Postgres by BenjieGillam on Saturday June 01, 2019 @03:14AM (#20067803)
I suspect many of these concerns were with PostgreSQL 9.5 and 9.6 where RLS did indeed have many performance issues. PG 10 fixed a large number of these issues, and PG11 even more. I would recommend re-evaluating RLS performance on these latest PostgreSQL versions.
Re:Scaling to 1M active GraphQL subscriptions on Postgres by aidos on Saturday June 01, 2019 @05:35AM (#20068337)
In Hasura’s use case it’s a little different. They’re working on the assumption that you have loads of identical queries that you want to run that differ only in the session variables (and hence the rows they see). Because they’re outside Postgres, they can collate it all and execute a single query for multiple users. Within Postgres you don’t have that luxury. It’s a trade off, but not using RLS suits some use cases better.
Re:Scaling to 1M active GraphQL subscriptions on Postgres by ndarilek on Saturday June 01, 2019 @08:02AM (#20068760)
Oh good, glad RLS performance got a boost. Unfortunately my Postgraphile implementation for that project was replaced with Drupal, but I'm glad RLS performance is less of a concern under version 10 and up.