More than a refresh: Conversations with the most interesting people you've never met podkast

MTAR T3D Sessions: Why PostgreSQL’s Extended Query Protocol Complicates Caching

0:00
15:14
Do tyłu o 15 sekund
Do przodu o 15 sekund

Serving a query from cache gets more complicated when PostgreSQL still needs to know which statements have been prepared and bound. For James Nelson, founder and CTO of PgCache, keeping that state consistent is what makes the extended query protocol his Postgres pet peeve.

In this installment of Postgres Pet Peeves, James explains how his caching proxy tracks prepared statements and forwards preparation messages to PostgreSQL when they become necessary. A wrong message or response can put the connection out of sync and cause it to be terminated. He and JD explore that coordination work, along with how PgCache falls back to PostgreSQL when needed and exposes its internal behavior through Prometheus metrics.

The conversation also turns to PgCache’s source-available license and the trade-off between protecting a business and encouraging outside contributions. James shares why he and his co-founder chose a more restrictive starting point, while JD makes the case for a permissive open source license.

Więcej odcinków z kanału "More than a refresh: Conversations with the most interesting people you've never met"