This blog post works through some common PostgreSQL performance opportunities while teaching you about the common ailments and decision-making that you need to make around indexing with PostgreSQL.

The target audience is for TypeScript/JavaScript developers who understand the basics of interfacing with PostgreSQL, but do not yet feel confident in working directly with SQL or the impacts of certain table design decisions. For those more confident with their PostgreSQL capabilities, this post will not be anymore than a reference for you.

We will be using Prisma to abstract some of the table schema design work. This is purely to lower the barrier to entry for developers so we can spend more take talking about and showing improvements.

I've chosen Prisma primarily as it helps for me to share this piece with work colleagues at my workplace (at the time of writing), but note that what is shown focuses more on PostgreSQL and is not ORM-bound.

Photo credit: aleksdahlberg