Prisma Query Logging and PostgreSQL: Where the ORM Ends and the Database Begins
The article discusses the limitations of Prisma's query logging in relation to PostgreSQL database performance. 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 query logs show the query and its duration from the ORM's perspective, not the actual execution time in PostgreSQL.
- ▪To accurately measure execution time in PostgreSQL, tools like pg_stat_statements or EXPLAIN ANALYZE should be used.
- ▪Confusing client duration with PostgreSQL execution time can lead to incorrect assumptions about query performance.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
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-and-postgresql-where-the-orm-ends-and-the-database-begins-34k3 |
| Publication time | Mon, 25 May 2026 14:30:35 +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)
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.
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 and PostgreSQL: Where the ORM Ends and the Database Begins #english #typescript #backend #nextjs Prisma Query Logging and PostgreSQL: Where the ORM Ends and the Database Begins I turned on query logging in Prisma, watched queries rolling into the console, and assumed I had full visibility into what was happening in the database. Spoiler: I didn't.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
