Prisma query logging y PostgreSQL: dónde termina el ORM y empieza la base

May 25, 2026 · 2:30 PM UTC ·9 min read · 0 reactions · 0 comments · 36 views

#postgresql #prisma #orm #database #logging

TL;DR · WeSearch summary

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.

Key facts

▪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.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/jtorchia/prisma-query-logging-y-postgresql-donde-termina-el-orm-y-empieza-la-base-6io
Publication time	Mon, 25 May 2026 14:30:31 +0000
Retrieval time	2026-05-25T14:37:38.029Z
Last seen	2026-05-25T14:37:38.029Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	NIM2LexQ4tm_ · 2 stories
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

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).

Anonymous · no account needed

Discussion

0 comments