pg_stat_statements und pg_buffercache verwenden
Nutzen Sie leistungsfähige Erweiterungen wie `pg_stat_statements` und `pg_buffercache`, um detaillierte Einblicke in die Performance zu gewinnen.
pg_stat_statements und pg_buffercache verwenden ist eine kostenlose PostgreSQL Performance & Query Optimization-Lektion auf CoddyKit. Dies ist Lektion 1 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des PostgreSQL Performance & Query Optimization-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der PostgreSQL Performance & Query Optimization-Kurs umfasst insgesamt 4 Lektionen.
Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.
PostgreSQL Extensions: Power-Ups
PostgreSQL is incredibly powerful, and its functionality can be extended even further using extensions.
Extensions are modules that add new functions, data types, operators, and more to your database. They're like plugins that enhance your database's capabilities without modifying its core code.
In this lesson, we'll explore two crucial extensions for performance monitoring: pg_stat_statements and pg_buffercache.
Meet pg_stat_statements: Query Profiler
pg_stat_statements is an invaluable tool for understanding your database's workload. It tracks execution statistics for all SQL statements executed by the server.
This extension helps you identify:
- Which queries are run most frequently.
- Which queries consume the most total time.
- Queries with high average execution times.
- Queries that read/write a lot of disk blocks.
It's your go-to for pinpointing performance bottlenecks at the query level.
Activating pg_stat_statements
To use pg_stat_statements, you first need to enable it in your PostgreSQL configuration.
1. Edit your postgresql.conf file and add pg_stat_statements to the shared_preload_libraries parameter. E.g., shared_preload_libraries = 'pg_stat_statements'.
2. Restart your PostgreSQL server for the change to take effect.
3. Finally, connect to your database and create the extension:
CREATE EXTENSION pg_stat_statements;Deciphering pg_stat_statements Output
Once enabled, pg_stat_statements collects data in a view named pg_stat_statements. Here are some key columns you'll often check:
query: The normalized SQL statement.calls: How many times the query was executed.total_time: Total time spent executing this query (in milliseconds).mean_time: Average execution time per call.rows: Total rows returned or affected.shared_blks_hit/shared_blks_read: Cache hits vs. disk reads.
Sorting by total_time helps find the biggest overall resource consumers.
Practical Example: Top Queries
Let's see how to find the top 5 queries that have consumed the most total execution time. This query helps you prioritize your optimization efforts.
The hit_percent column gives you an idea of how effective PostgreSQL's buffer cache is for that query.
SELECT
query,
calls,
total_time,
mean_time,
rows,
100.0 * shared_blks_hit / (shared_blks_hit + shared_blks_read + 1) AS hit_percent
FROM
pg_stat_statements
ORDER BY
total_time DESC
LIMIT 5;Meet pg_buffercache: Memory Inspector
While pg_stat_statements shows you query performance, pg_buffercache gives you insight into PostgreSQL's shared buffer cache. This is the memory area where PostgreSQL stores frequently accessed data blocks.
Understanding what's in the buffer cache helps you determine:
- Which tables or indexes are most actively used.
- If your
shared_bufferssetting is adequate. - Whether queries are benefiting from cached data or hitting disk.
Activating pg_buffercache
Enabling pg_buffercache is simpler than pg_stat_statements. It typically does not require modification to shared_preload_libraries or a server restart.
You just need to connect to your database and create the extension:
CREATE EXTENSION pg_buffercache;Peeking into the Shared Buffer Cache
After creating the extension, you can query the pg_buffercache view to see which relations (tables or indexes) occupy the most buffers. Each buffer typically represents an 8KB data block.
This query shows the top 5 relations by the number of buffers they occupy in the cache:
SELECT
c.relname AS relation_name,
count(*) AS buffers_in_cache
FROM
pg_buffercache b
JOIN
pg_class c ON b.relfilenode = c.relfilenode
JOIN
pg_database d ON b.reldatabase = d.oid AND d.datname = current_database()
GROUP BY
c.relname
ORDER BY
buffers_in_cache DESC
LIMIT 5;Interpreting Cache Effectiveness
If a table or index consistently appears at the top of the pg_buffercache output with many buffers, it means that data is frequently accessed and kept in memory.
This is generally a good sign, as memory access is much faster than disk I/O. A high hit_percent in pg_stat_statements often correlates with data being present in the buffer cache.
You can use this information to decide if increasing shared_buffers or optimizing queries to access less data would be beneficial.
Quick Check: Monitoring Tools
Which of the following statements are true regarding pg_stat_statements and pg_buffercache?
Recap: Deep Dives with Extensions
Great job! You've learned how to leverage two powerful PostgreSQL extensions for performance monitoring:
pg_stat_statements: Your essential tool for profiling SQL queries, identifying slow-running or frequently executed statements, and understanding their resource consumption.pg_buffercache: Gives you visibility into the shared buffer cache, helping you understand what data is actively residing in memory and how effectively your caching is working.
Combined, these extensions provide deep insights into your database's workload and memory utilization, guiding your optimization efforts.
Häufig gestellte Fragen
Ist die Lektion „pg_stat_statements und pg_buffercache verwenden“ kostenlos?
Ja — der vollständige Text von „pg_stat_statements und pg_buffercache verwenden“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des PostgreSQL Performance & Query Optimization-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der PostgreSQL Performance & Query Optimization-Kurs umfasst insgesamt 4 Lektionen.
Was lerne ich in „pg_stat_statements und pg_buffercache verwenden“?
Nutzen Sie leistungsfähige Erweiterungen wie `pg_stat_statements` und `pg_buffercache`, um detaillierte Einblicke in die Performance zu gewinnen. Du übst PostgreSQL Performance & Query Optimization mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.
Brauche ich Erfahrung, um PostgreSQL Performance & Query Optimization zu starten?
Keine Vorkenntnisse erforderlich. PostgreSQL Performance & Query Optimization auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 1 von 4.
Wie lange dauert die Lektion „pg_stat_statements und pg_buffercache verwenden“?
Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.
Kann ich in dieser PostgreSQL Performance & Query Optimization-Lektion Code schreiben und ausführen?
Ja. Jede PostgreSQL Performance & Query Optimization-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.
Alle Lektionen in diesem Kurs
- pg_stat_statements und pg_buffercache verwenden
- Logging-Konfiguration für Analysen
- Integration externer Monitoring-Tools
- Laufende Aktivitäten mit pg_stat_activity diagnostizieren