Prisma query logging y PostgreSQL: dónde termina el ORM y empieza la base
The article discusses the limitations of Prisma's query logging in relation to PostgreSQL performance diagnostics. It emphasizes that while Prisma logs provide insights into query execution from the ORM's perspective, they do not reflect the actual execution time within PostgreSQL. The author warns against confusing client-side duration with database execution time, which can lead to misguided optimization efforts.
- ▪Prisma's query logs show the time taken from the ORM's perspective, including network latency and serialization overhead.
- ▪To accurately measure execution time in PostgreSQL, tools like pg_stat_statements or EXPLAIN ANALYZE should be used.
- ▪Confusing the duration reported by Prisma with actual database execution time can result in incorrect diagnostics and unnecessary optimizations.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 885942) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Juan Torchia Posted on May 25 • Originally published at juanchi.dev Prisma query logging y PostgreSQL: dónde termina el ORM y empieza la base #spanish #espanol #typescript #backend Prisma query logging y PostgreSQL: dónde termina el ORM y empieza la base Activé query logging en Prisma, vi los queries llegando a la consola, y asumí que tenía visibilidad completa sobre lo que pasaba en la base. Spoiler: no la tenía.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
