A tenant holding two percent of your rows can come back empty, no error and nothing in the logs. ...

A tenant holding two percent of your rows can come back empty, no error and nothing in the logs. ...A tenant holding two percent of your rows can come back empty, no error and nothing in the logs. ...

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Dusko Licanin

pro

• Aug 3

A tenant holding two percent of your rows can come back empty, no error and nothing in the logs.

HNSW returns roughly 40 candidates by default and the tenant filter eats most of them before they reach your app. Iterative scans in pgvector 0.8, or a partial index per tenant, sorts it.

Where I'd stop and reach for something else → https://www.duskolicanin.com/blog/postgres-pgvector-ai-saas-2026

Database Engineering Supabase TypeScript

Dusko Licanin

pro

• Aug 2

I reviewed a dashboard last month where the delete action trusted the tenant id handed to it. No check, because the button calling it already sat behind auth.

That's the shape of all four Server Action CVEs this year, one a 10.0. The boundary moved off the client and the validation didn't follow.

Where I draw the line now → https://www.duskolicanin.com/blog/server-components-saas-patterns-2026