3 ms·
We use the tool that I wrote on a database with tens of millions of rows. Because the keys are properly indexed, we rarely have performance issues associated wi
by pjs_ 2y ago
We use the tool that I wrote on a database with tens of millions of rows. Because the keys are properly indexed, we rarely have performance issues associated with joins. Joins use the index, the Postgres planner is really good, and we can join across heaps of tables with great performance.
We have database performance issues for other reasons (loading of redundant information, too many queries) but not really because of joins.