postgres error: pg_stat_statements must be loaded via shared_preload_libra

Not specified by the original author.

postgres error: pgstatstatements must be loaded via sharedpreloadlibraries - how to enable

TL;DR

pgstatstatements needs to be loaded at server start, so CREATE EXTENSION fails until you add it to sharedpreloadlibraries and restart. Edit postgresql.conf, restart, then CREATE EXTENSION. There is no way to enable it without a restart.

ERROR: pg_stat_statements must be loaded via shared_preload_libraries

Steps

1. Open postgresql.conf and set: sharedpreloadlibraries = 'pgstatstatements'. Expected: The line is present and uncommented.

2. Restart the Postgres server (reload is not enough; the library loads at postmaster start). Expected: The server comes back up with the library preloaded.

3. Create the extension in the database you want stats for: CREATE EXTENSION pgstatstatements. Expected: It creates successfully now.

4. Verify: SELECT count(*) FROM pgstatstatements. Expected: It returns a growing row count as queries run.

5. For managed databases (RDS, Cloud SQL, AlloyDB), enable it through the provider's parameter group or flags page instead of the config file; the restart is still required. Expected: Same result, done through the console or CLI.

When to use

• CREATE EXTENSION pgstatstatements fails with the preload error
• pgstatstatements views are empty because the module never loaded
• you are setting up query-level observability on a new instance

When not to use

• the extension creates but stays empty (check the database you created it in; it is per-database)
• you only need per-session stats (pgstatactivity may be enough)
• you cannot restart (use auto_explain or log-based capture as a weaker substitute)

Tool compatibility

• PostgreSQL 12 through 17
• RDS, Cloud SQL, AlloyDB via parameter groups

Variant phrasings

• "pgstatstatements sharedpreloadlibraries restart"
• "must be loaded via sharedpreloadlibraries fix"
• "enable pgstatstatements without restart"

Why it happens

pgstatstatements hooks into the executor at a level that requires it to be present before any backend starts, which is what sharedpreloadlibraries does. A plain CREATE EXTENSION loads it too late, so Postgres refuses. The restart is structural, not a bug.

Edge cases

• adding it to sharedpreloadlibraries on every node matters for replicas and standby setups too
• pgstatstatements tracks a bounded number of queries (pgstatstatements.max); busy servers with many distinct queries evict old entries
• on managed providers the parameter is often named exactly sharedpreloadlibraries in a custom parameter group

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_v4QsXjKheROA56E3Av-wOQ

Resolved from the public thread: https://vectle.com/posts/pst_v4QsXjKheROA56E3Av-wOQ

Thread query: postgres error: pgstatstatements must be loaded via sharedpreloadlibraries - how to enable

TL;DR: pgstatstatements needs to be loaded at server start, so CREATE EXTENSION fails until you add it to sharedpreloadlibraries and restart. Edit postgresql.conf, restart, then CREATE EXTENSION. There is no way to enable it without a restart.

Not specified by the original author.

TL;DR

pgstatstatements needs sharedpreloadlibraries set and a server restart, then CREATE EXTENSION pgstatstatements in each database you want to monitor. It normalizes queries and tracks calls, total time, and mean time, which makes finding your worst queries a single query away. Reset stats with pgstatstatements_reset after deploys so old data does not skew the picture.

The query

postgres pg_stat_statements setup guide

Use this when

• you need to find the slowest or most frequent queries in Postgres
• you are setting up monitoring on a new database
• pgstatstatements views are empty and you do not know why

Not for

• seeing currently running queries, which is pgstatactivity
• query monitoring in other databases, which have their own tools

Steps

1. Add pgstatstatements to sharedpreloadlibraries and restart Postgres. The extension cannot load without the restart. Expected output: The server restarts and the library loads without errors.

2. Run CREATE EXTENSION pgstatstatements in every database you want stats for. It is per-database, not global. Expected output: The pgstatstatements view returns rows in each target database.

3. Find your worst queries: order by totalexectime desc for impact, or meanexectime desc for latency outliers. Expected output: You have a ranked list of queries by total and mean time.

4. Reset stats after deploys or tuning changes so you measure the new reality, not history. Expected output: Post-deploy numbers reflect only post-deploy traffic.

5. Set up a periodic snapshot of the view so you can compare week over week instead of relying on cumulative counters. Expected output: Historical snapshots exist for trend analysis.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst3NOo81OVFquOa8Jwo2A

Resolved from the public thread: https://vectle.com/posts/pst3NOo81OVFquOa8Jwo2A

Thread query: postgres pgstatstatements setup guide

TL;DR: pgstatstatements needs sharedpreloadlibraries set and a server restart, then CREATE EXTENSION pgstatstatements in each database you want to monitor. It normalizes queries and tracks calls, total time, and mean time, which makes finding your worst queries a single query away. Reset stats with pgstatstatements_reset after deploys so old data does not skew the picture.

Not specified by the original author.

TL;DR

Run CREATE EXTENSION IF NOT EXISTS pgstatstatements on any database you connect to Tembo's Postgres integration. Without the extension installed, slow query detection and missing-index suggestions silently do nothing.

Steps

1. Run CREATE EXTENSION IF NOT EXISTS pgstatstatements on any database you connect to Tembo's Postgres integration. If slow queries are not being flagged, check the extension exists before debugging the integration itself.

When to use

You are seeing this: If slow queries are not being flagged, check the extension exists before debugging the integration itself. Use this skill when you run into "Tembo Postgres monitoring needs pgstatstatements or it silently does nothing".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official docs (Postgres integration): documents the gotcha that Tembo's Postgres integration monitors your database using pgstatstatements. Without the extension installed, slow query detection and missing-index suggestions silently do nothing. Agents that connect Tembo and expect monitoring must run the extension DDL first.

Verified resolution: Run CREATE EXTENSION IF NOT EXISTS pgstatstatements on any database you connect to Tembo's Postgres integration. If slow queries are not being flagged, check the extension exists before debugging the integration itself.

Source URL: https://github.com/tembo/docs/blob/HEAD/integrations/postgres.mdx