> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Postgres Query Latency p95 (ms), Supabase

> Postgres Query Latency p95 (ms) for Supabase projects. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

**Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained)  •  **Category:** [Performance](/nerve-centre/connectors#connectors-by-type)

## At a glance

> **Postgres Query Latency p95 (ms)** is the 95th-percentile execution time of statements run against your Supabase Postgres instance over the selected period. Ninety-five out of every hundred queries complete faster than this number; the slowest five percent take longer. It is the headline read on database responsiveness, and it climbs before users notice, so it is an early warning rather than a lagging one.

A high p95 means the slow tail of your workload is dragging: missing indexes, lock contention, a bloated table, or a connection pool under pressure are the usual causes. The card pairs with the latency, slow-query, and pool-saturation siblings to localise the cause before it becomes a checkout-window problem.

## What it tracks

The card reports Postgres Query Latency p95 (ms) for the selected period, sampled in real time on a rolling 5-minute window (`RT/5m`). The value is the p95 of statement execution time as seen by the database, not round-trip time from the client, so network and Supavisor pooling overhead are excluded. The alert fires when p95 sustains above 200ms, the point at which the slow tail starts to show up in user-facing requests. Roles: engineering, operations. Read it next to [Slow Query Rate](/nerve-centre/kpi-cards/supabase/slow-query-rate) and [Top 10 Slowest Queries](/nerve-centre/kpi-cards/supabase/top-10-slowest-queries) when it climbs.

## Reconciling against the source

Confirm the number against Supabase's own tooling: enable the `pg_stat_statements` extension and query `SELECT query, mean_exec_time, max_exec_time, calls FROM pg_stat_statements ORDER BY mean_exec_time DESC` for per-statement timings, or open the Query Performance and Reports pages in the Supabase project dashboard for the managed-service view. Note that `pg_stat_statements` reports mean and max per statement rather than a true cross-statement percentile, so expect approximate, not exact, agreement with the card's p95.

***

### Tracked live in Vortex IQ Nerve Centre

*Postgres Query Latency p95 (ms)* is one of hundreds of KPI pulses Vortex IQ tracks across Supabase and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

[Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.