blog/npgsqlrest-vs-postgrest-supabase-comparison

[giscus[bot]]

blog/npgsqlrest-vs-postgrest-supabase-comparison

Side-by-side comparison of NpgsqlRest, PostgREST, and Supabase. Performance benchmarks, features, authentication, file handling, and deployment options compared.

https://npgsqlrest.github.io/blog/npgsqlrest-vs-postgrest-supabase-comparison.html

[qdrddr]

Can I replace PostgREST with NpgsqlRest and use with Supabase?

[vbilopav]

Not really. It's not in-place replacement, it needs adjustments. Differences are described in this document.

Most notably:

• Table and View Query Features. I prefer function/procedure approach and when it comes to direct table access (which I hate), NpgsqlRest has only basic features compared to PostgREST. Instead of reaching feature parity with PostgREST I am thinking even to remove even basic direct table access features. But it is available for now.

• PostgrREST (and Supabase which uses PostgrREST) is using RLS for authorization levels:

create policy "Users can view own data"
  on users for select
  using (auth.uid() = id);

NpgsqlRest is using comment annotation and role-based security:

comment on function api.get_user(int) is '
HTTP GET
@authorize admin, user
';

RLS adds hidden filter and messes up indexing and partition strategies. I hate it and I tend to avoid RLS anywhere I can.

Also, NpgsqlRest promotes unique per-endpoint configuration. With PostgrREST/Supabase you configure all or nothing.

So answer is no. See Migration Considerations for more details.