{"id":241,"date":"2026-11-16T06:10:00","date_gmt":"2026-11-16T06:10:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/?p=241"},"modified":"2026-11-16T06:10:00","modified_gmt":"2026-11-16T06:10:00","slug":"pg-stat-statements-yavas-sorgu-bulma","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/16\/pg-stat-statements-yavas-sorgu-bulma\/","title":{"rendered":"pg_stat_statements ile En Pahal\u0131 Sorgular\u0131 Bulmak"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>pg_stat_statements<\/strong>, PostgreSQL&#8217;in \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131 her sorgu tipi i\u00e7in \u00e7a\u011fr\u0131 say\u0131s\u0131n\u0131, toplam ve ortalama s\u00fcreyi, okunan sayfa say\u0131s\u0131n\u0131 ve d\u00f6nen sat\u0131r say\u0131s\u0131n\u0131 biriktiren resmi bir eklentidir. Veritaban\u0131 yava\u015flad\u0131\u011f\u0131nda &#8220;hangi sorgu?&#8221; sorusunun cevab\u0131n\u0131 tahmin yerine veriyle verir. Ben bir PostgreSQL sunucusunda performans \u00e7al\u0131\u015fmas\u0131na ba\u015flarken ilk bakt\u0131\u011f\u0131m yer buras\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu yaz\u0131da eklentiyi nas\u0131l a\u00e7aca\u011f\u0131n\u0131z\u0131, sonu\u00e7lar\u0131 hangi s\u0131raya g\u00f6re okuman\u0131z gerekti\u011fini ve en s\u0131k yap\u0131lan yorum hatalar\u0131n\u0131 anlataca\u011f\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">pg_stat_statements neden gerekli?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Yava\u015f sorgu loglar\u0131 (<code>log_min_duration_statement<\/code>) tek tek yava\u015f sorgular\u0131 yakalar. Bu faydal\u0131d\u0131r ama resmin yar\u0131s\u0131d\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir sorgu 3 ms s\u00fcr\u00fcyor ve dakikada 50.000 kez \u00e7a\u011fr\u0131l\u0131yorsa, hi\u00e7bir zaman yava\u015f sorgu loguna d\u00fc\u015fmez. Ama veritaban\u0131n\u0131n toplam zaman\u0131n\u0131n b\u00fcy\u00fck k\u0131sm\u0131n\u0131 o t\u00fcketiyordur. Tersine, ayda bir \u00e7al\u0131\u015fan 40 saniyelik bir rapor sorgusu logda g\u00f6ze \u00e7arpar ama toplam y\u00fckte \u00f6nemsizdir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">pg_stat_statements bu ikisini ayn\u0131 tabloda g\u00f6sterir. Sorgular normalize edilir: <code>WHERE id = 42<\/code> ve <code>WHERE id = 97<\/code> ayn\u0131 sat\u0131rda <code>WHERE id = $1<\/code> olarak toplan\u0131r. B\u00f6ylece ayn\u0131 sorgunun binlerce farkl\u0131 parametreyle \u00e7al\u0131\u015fmas\u0131 tek bir kay\u0131tta birikir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kurulum nas\u0131l yap\u0131l\u0131r?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eklenti PostgreSQL ile birlikte gelir ama varsay\u0131lan olarak y\u00fcklenmez. \u0130ki ad\u0131m gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00d6nce <code>postgresql.conf<\/code> i\u00e7inde payla\u015f\u0131ml\u0131 k\u00fct\u00fcphane olarak eklenir. Bu de\u011fi\u015fiklik yeniden ba\u015flatma gerektirir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>shared_preload_libraries = 'pg_stat_statements'\npg_stat_statements.track = top\npg_stat_statements.max = 10000<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Sonra veritaban\u0131nda eklenti olu\u015fturulur:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>CREATE EXTENSION IF NOT EXISTS pg_stat_statements;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Y\u00f6netilen servislerde, \u00f6rne\u011fin Amazon RDS, Cloud SQL veya Azure Database for PostgreSQL&#8217;de, eklenti genellikle parametre grubu \u00fczerinden a\u00e7\u0131l\u0131r ve \u00e7o\u011funda varsay\u0131lan olarak y\u00fckl\u00fc gelir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ek y\u00fck\u00fc d\u00fc\u015f\u00fckt\u00fcr. Ben production sunucular\u0131nda kapal\u0131 tutmak i\u00e7in ge\u00e7erli bir sebep g\u00f6rmedim. As\u0131l risk, kapal\u0131 oldu\u011fu i\u00e7in bir performans probleminde elinizde hi\u00e7bir veri olmamas\u0131d\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hangi kolonlar ne anlat\u0131r?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00f6r\u00fcn\u00fcmde onlarca kolon var. G\u00fcnl\u00fck kullan\u0131mda bakt\u0131\u011f\u0131m kolonlar s\u0131n\u0131rl\u0131. A\u015fa\u011f\u0131daki isimler PostgreSQL 13 ve sonras\u0131 i\u00e7indir. Daha eski s\u00fcr\u00fcmlerde <code>total_time<\/code> gibi farkl\u0131 adlar kullan\u0131l\u0131yordu.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Kolon<\/th><th>Anlam\u0131<\/th><\/tr><\/thead><tbody><tr><td>calls<\/td><td>Sorgunun ka\u00e7 kez \u00e7al\u0131\u015ft\u0131\u011f\u0131<\/td><\/tr><tr><td>total_exec_time<\/td><td>B\u00fct\u00fcn \u00e7al\u0131\u015ft\u0131rmalar\u0131n toplam s\u00fcresi, ms<\/td><\/tr><tr><td>mean_exec_time<\/td><td>Ortalama s\u00fcre, ms<\/td><\/tr><tr><td>stddev_exec_time<\/td><td>S\u00fcrenin standart sapmas\u0131<\/td><\/tr><tr><td>rows<\/td><td>D\u00f6nen veya etkilenen toplam sat\u0131r<\/td><\/tr><tr><td>shared_blks_hit<\/td><td>Bellekten okunan sayfa say\u0131s\u0131<\/td><\/tr><tr><td>shared_blks_read<\/td><td>Diskten okunan sayfa say\u0131s\u0131<\/td><\/tr><tr><td>temp_blks_written<\/td><td>Bellek yetmedi\u011fi i\u00e7in diske yaz\u0131lan ge\u00e7ici sayfalar<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><code>temp_blks_written<\/code> kolonu s\u0131k atlan\u0131r ama de\u011ferlidir. S\u0131f\u0131rdan b\u00fcy\u00fckse sorgu, s\u0131ralama veya hash i\u015flemi i\u00e7in <code>work_mem<\/code> s\u0131n\u0131r\u0131n\u0131 a\u015fm\u0131\u015f ve ge\u00e7ici dosya kullanm\u0131\u015ft\u0131r. Bu hem diski yorar hem de sorguyu yava\u015flat\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>rows<\/code> kolonunu <code>calls<\/code> de\u011ferine b\u00f6lmek, sorgunun her \u00e7al\u0131\u015ft\u0131rmada ortalama ka\u00e7 sat\u0131r d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc verir. Bir liste ekran\u0131 i\u00e7in \u00e7al\u0131\u015fan sorgunun her seferinde 50.000 sat\u0131r d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc g\u00f6rmek, pagination eksikli\u011fini veya uygulama taraf\u0131nda filtreleme yap\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6sterir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shared_blks_hit<\/code> ve <code>shared_blks_read<\/code> toplam\u0131n\u0131 <code>rows<\/code> de\u011ferine b\u00f6lmek de faydal\u0131 bir oran. D\u00f6nd\u00fcr\u00fclen sat\u0131r ba\u015f\u0131na okunan sayfa say\u0131s\u0131 \u00e7ok y\u00fcksekse, sorgu ihtiyac\u0131ndan \u00e7ok daha fazla veriyi geziyor demektir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Sonu\u00e7lar hangi s\u0131raya g\u00f6re okunmal\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ayn\u0131 veri farkl\u0131 s\u0131ralamalarla farkl\u0131 sorular cevaplar. Ben genellikle d\u00f6rt sorgu \u00e7al\u0131\u015ft\u0131r\u0131yorum.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Toplam s\u00fcreye g\u00f6re<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Veritaban\u0131n\u0131n zaman\u0131n\u0131 en \u00e7ok nereye harcad\u0131\u011f\u0131n\u0131 g\u00f6sterir. Optimizasyon i\u00e7in en de\u011ferli s\u0131ralama budur.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SELECT\n  round(total_exec_time::numeric, 0) AS total_ms,\n  calls,\n  round(mean_exec_time::numeric, 2) AS mean_ms,\n  round(100 * total_exec_time \/ sum(total_exec_time) OVER (), 1) AS pct,\n  left(query, 120) AS query\nFROM pg_stat_statements\nORDER BY total_exec_time DESC\nLIMIT 20;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>pct<\/code> kolonu, sorgunun toplam s\u00fcre i\u00e7indeki pay\u0131n\u0131 g\u00f6sterir. Listenin ilk birka\u00e7 sat\u0131r\u0131 \u00e7o\u011fu zaman toplam s\u00fcrenin yar\u0131s\u0131ndan fazlas\u0131n\u0131 olu\u015fturur. Optimizasyona oradan ba\u015flamak, en az eforla en fazla etkiyi verir.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ortalama s\u00fcreye g\u00f6re<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Tek ba\u015f\u0131na yava\u015f olan sorgular\u0131 g\u00f6sterir. Kullan\u0131c\u0131n\u0131n bekledi\u011fi bir ekran\u0131n arkas\u0131ndaki sorgu burada \u00e7\u0131k\u0131yorsa, toplam y\u00fckte k\u00fc\u00e7\u00fck g\u00f6r\u00fcnse bile \u00f6nemlidir.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u00c7a\u011fr\u0131 say\u0131s\u0131na g\u00f6re<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Beklenmedik derecede s\u0131k \u00e7al\u0131\u015fan sorgular\u0131 ortaya \u00e7\u0131kar\u0131r. Bir sayfa y\u00fcklemesinde ayn\u0131 sorgunun y\u00fczlerce kez \u00e7al\u0131\u015fmas\u0131, genellikle ORM kaynakl\u0131 bir N+1 probleminin i\u015faretidir. Bu kal\u0131b\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/14\/orm-n-plus-one-query\/\">N+1 problemi<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131 anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Okunan sayfa say\u0131s\u0131na g\u00f6re<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><code>shared_blks_read<\/code> ve <code>shared_blks_hit<\/code> kolonlar\u0131, sorgunun bellekten mi diskten mi okudu\u011funu g\u00f6sterir. \u00c7ok sayfa okuyup az sat\u0131r d\u00f6nd\u00fcren sorgular, eksik index i\u00e7in en g\u00fc\u00e7l\u00fc adaylard\u0131r.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>S\u0131ralama<\/th><th>Cevaplad\u0131\u011f\u0131 soru<\/th><th>Tipik bulgu<\/th><\/tr><\/thead><tbody><tr><td>total_exec_time<\/td><td>Veritaban\u0131 zaman\u0131n\u0131 nereye harc\u0131yor?<\/td><td>S\u0131k \u00e7al\u0131\u015fan, orta h\u0131zda sorgular<\/td><\/tr><tr><td>mean_exec_time<\/td><td>Tek ba\u015f\u0131na hangi sorgu yava\u015f?<\/td><td>Rapor ve arama sorgular\u0131<\/td><\/tr><tr><td>calls<\/td><td>Hangi sorgu beklenenden s\u0131k \u00e7al\u0131\u015f\u0131yor?<\/td><td>N+1, gereksiz kontrol sorgular\u0131<\/td><\/tr><tr><td>shared_blks_read<\/td><td>Hangi sorgu en \u00e7ok disk okuyor?<\/td><td>Eksik index, b\u00fcy\u00fck taramalar<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Bir sorguyu bulduktan sonra ne yapmal\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">pg_stat_statements size hangi sorguya bakman\u0131z gerekti\u011fini s\u00f6yler. Neden yava\u015f oldu\u011funu s\u00f6ylemez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Normalize edilmi\u015f sorgudaki <code>$1<\/code>, <code>$2<\/code> parametrelerini ger\u00e7ek\u00e7i de\u011ferlerle doldurup <code>EXPLAIN (ANALYZE, BUFFERS)<\/code> ile \u00e7al\u0131\u015ft\u0131rmak bir sonraki ad\u0131md\u0131r. Plan okuman\u0131n ayr\u0131nt\u0131lar\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/13\/postgresql-explain-analyze-nasil-okunur\/\">EXPLAIN ANALYZE nas\u0131l okunur<\/a> yaz\u0131s\u0131nda anlatt\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Parametre se\u00e7imi \u00f6nemli. \u00c7arp\u0131k da\u011f\u0131l\u0131ma sahip verilerde, bir m\u00fc\u015fteri i\u00e7in h\u0131zl\u0131 \u00e7al\u0131\u015fan sorgu ba\u015fka bir m\u00fc\u015fteri i\u00e7in \u00e7ok yava\u015f olabilir. Ger\u00e7ek uygulama trafi\u011finden \u00f6rnek parametreler almak, test de\u011ferleriyle \u00e7al\u0131\u015fmaktan daha do\u011fru sonu\u00e7 verir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">S\u0131k yap\u0131lan yorum hatalar\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Ortalamaya g\u00fcvenmek.<\/strong> <code>mean_exec_time<\/code> bir ortalama. Sorgunun \u00e7o\u011fu zaman 2 ms, bazen 4 saniye s\u00fcrd\u00fc\u011f\u00fc durumlar\u0131 gizler. <code>stddev_exec_time<\/code> ve <code>max_exec_time<\/code> kolonlar\u0131 bu da\u011f\u0131l\u0131m hakk\u0131nda fikir verir. Ortalaman\u0131n neden yan\u0131lt\u0131c\u0131 oldu\u011funu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/11\/latency-percentiles-load-testing\/\">yan\u0131t s\u00fcresi y\u00fczdelikleri<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>\u0130statistiklerin ne zamandan beri birikti\u011fini bilmemek.<\/strong> De\u011ferler sunucu ba\u015flad\u0131\u011f\u0131ndan veya son s\u0131f\u0131rlamadan beri birikir. \u00dc\u00e7 ay \u00f6nce d\u00fczeltilmi\u015f bir sorgu, h\u00e2l\u00e2 listenin ba\u015f\u0131nda g\u00f6r\u00fcnebilir. Bir optimizasyonun etkisini \u00f6l\u00e7mek i\u00e7in \u00f6ncesinde <code>pg_stat_statements_reset()<\/code> \u00e7al\u0131\u015ft\u0131r\u0131p belirli bir s\u00fcre sonra tekrar bakmak gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Planlama s\u00fcresini g\u00f6rmezden gelmek.<\/strong> <code>track_planning<\/code> a\u00e7\u0131ksa planlama s\u00fcresi de g\u00f6r\u00fcl\u00fcr. \u00c7ok karma\u015f\u0131k ve \u00e7ok s\u0131k \u00e7al\u0131\u015fan sorgularda planlama s\u00fcresi, \u00e7al\u0131\u015fma s\u00fcresine yakla\u015fabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tek bir anl\u0131k g\u00f6r\u00fcnt\u00fcye bakmak.<\/strong> Bug\u00fcn\u00fcn de\u011ferleri tek ba\u015f\u0131na trend g\u00f6stermez. De\u011ferleri d\u00fczenli olarak bir metrik sistemine aktarmak, bir deploy&#8217;dan sonra hangi sorgunun yava\u015flad\u0131\u011f\u0131n\u0131 g\u00f6rmeyi sa\u011flar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">De\u011ferleri izleme sistemine almak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">pg_stat_statements k\u00fcm\u00fclatif saya\u00e7lar tutar. Prometheus&#8217;un <code>postgres_exporter<\/code> arac\u0131 bu saya\u00e7lar\u0131 metrik olarak d\u0131\u015fa aktarabilir. Grafana&#8217;da sorgu baz\u0131nda saniyedeki \u00e7a\u011fr\u0131 say\u0131s\u0131n\u0131 ve s\u00fcre de\u011fi\u015fimini g\u00f6rmek, &#8220;d\u00fcn ak\u015fam deploy&#8217;dan sonra ne de\u011fi\u015fti?&#8221; sorusunu cevaplamay\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Uygulama taraf\u0131ndaki metriklerle birle\u015ftirildi\u011finde resim tamamlan\u0131r. Endpoint baz\u0131nda yan\u0131t s\u00fcresi art\u0131\u015f\u0131 ile veritaban\u0131nda belirli bir sorgunun s\u00fcresinin art\u0131\u015f\u0131n\u0131 ayn\u0131 zaman ekseninde g\u00f6rmek, k\u00f6k sebebi bulmay\u0131 h\u0131zland\u0131r\u0131r. Bu \u00fc\u00e7 sinyali birlikte kullanma yakla\u015f\u0131m\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/04\/observability-logs-metrics-traces\/\">log, metric ve trace<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ger\u00e7ek bir \u00f6rnek<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir projede veritaban\u0131 CPU&#8217;su s\u00fcrekli y\u00fczde 80&#8217;in \u00fczerindeydi. Yava\u015f sorgu loglar\u0131nda dikkat \u00e7eken bir \u015fey yoktu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">pg_stat_statements&#8217;\u0131 toplam s\u00fcreye g\u00f6re s\u0131ralad\u0131\u011f\u0131m\u0131zda ilk sat\u0131rda \u015fu vard\u0131:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>total_ms  calls     mean_ms  pct   query\n2841920   9184220   0.31     38.4  SELECT ... FROM user_settings WHERE user_id = $1<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Tek \u00e7al\u0131\u015ft\u0131rmada 0,3 ms s\u00fcren masum bir sorgu, veritaban\u0131 zaman\u0131n\u0131n y\u00fczde 38&#8217;ini t\u00fcketiyordu. Her API iste\u011finde, birka\u00e7 farkl\u0131 yerden, kullan\u0131c\u0131 ayarlar\u0131 tekrar tekrar okunuyordu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00c7\u00f6z\u00fcm veritaban\u0131nda de\u011fil uygulamadayd\u0131. Ayarlar\u0131 istek ba\u015f\u0131na bir kez okuyup ta\u015f\u0131mak ve s\u0131k de\u011fi\u015fmeyen veriyi k\u0131sa s\u00fcreli <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/09\/local-cache-caffeine-vs-redis\/\">local cache<\/a> i\u00e7inde tutmak, CPU kullan\u0131m\u0131n\u0131 y\u00fczde 45 civar\u0131na indirdi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu \u00f6rnek bence pg_stat_statements&#8217;\u0131n as\u0131l de\u011ferini g\u00f6steriyor. Tek tek h\u0131zl\u0131 g\u00f6r\u00fcnen ama toplamda pahal\u0131 olan \u015feyleri g\u00f6r\u00fcn\u00fcr k\u0131l\u0131yor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">pg_stat_statements&#8217;\u0131n s\u0131n\u0131rlar\u0131 nelerdir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eklenti \u00e7ok faydal\u0131 ama her \u015feyi g\u00f6stermez. S\u0131n\u0131rlar\u0131n\u0131 bilmek, yanl\u0131\u015f sonu\u00e7 \u00e7\u0131karmay\u0131 engeller.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Kilit beklemeleri ayr\u0131 g\u00f6r\u00fcnmez.<\/strong> Bir sorgunun s\u00fcresi, sat\u0131r kilidi i\u00e7in bekledi\u011fi zaman\u0131 da i\u00e7erir. Ortalama s\u00fcresi aniden artan bir <code>UPDATE<\/code> sorgusu yava\u015flamam\u0131\u015f, sadece ba\u015fka bir transaction&#8217;\u0131 bekliyor olabilir. Bu durumda <code>pg_stat_activity<\/code> ve <code>pg_locks<\/code> g\u00f6r\u00fcn\u00fcmleri anl\u0131k durumu g\u00f6sterir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>S\u0131n\u0131rl\u0131 say\u0131da sorgu tutulur.<\/strong> <code>pg_stat_statements.max<\/code> de\u011ferinden fazla farkl\u0131 sorgu olu\u015ftu\u011funda, en az \u00e7al\u0131\u015fanlar listeden d\u00fc\u015fer. Sorgu metni dinamik olarak \u00fcretiliyorsa, \u00f6rne\u011fin <code>IN<\/code> listesindeki eleman say\u0131s\u0131 her seferinde farkl\u0131ysa, ayn\u0131 sorgu y\u00fczlerce farkl\u0131 kay\u0131t olarak g\u00f6r\u00fcnebilir. PostgreSQL 18 bu konuda iyile\u015ftirme getirdi ama eski s\u00fcr\u00fcmlerde dikkat etmek gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Hangi uygulamadan geldi\u011fi belli de\u011fildir.<\/strong> G\u00f6r\u00fcn\u00fcm kullan\u0131c\u0131y\u0131 ve veritaban\u0131n\u0131 g\u00f6sterir ama hangi servisin veya endpoint&#8217;in sorguyu \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131 g\u00f6stermez. Her servis i\u00e7in ayr\u0131 bir veritaban\u0131 kullan\u0131c\u0131s\u0131 tan\u0131mlamak veya sorgulara yorum sat\u0131r\u0131yla kaynak bilgisi eklemek bu bo\u015flu\u011fu kapat\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Uygulama taraf\u0131ndaki s\u00fcreyi g\u00f6stermez.<\/strong> Bir iste\u011fin 900 ms s\u00fcrmesinin 30 ms&#8217;si veritaban\u0131nda ge\u00e7iyorsa, sorun veritaban\u0131nda de\u011fildir. Ama sadece pg_stat_statements&#8217;a bakarak bunu anlayamazs\u0131n\u0131z. Uygulama taraf\u0131ndaki connection bekleme s\u00fcresini de \u00f6l\u00e7mek gerekir. Connection havuzunun yanl\u0131\u015f boyutland\u0131r\u0131lmas\u0131n\u0131n nas\u0131l bir darbo\u011faz yaratt\u0131\u011f\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/28\/database-connection-pool-sizing\/\">connection pool boyutland\u0131rma<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kontrol listesi<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>shared_preload_libraries<\/code> i\u00e7inde eklentiyi a\u00e7, <code>CREATE EXTENSION<\/code> ile olu\u015ftur.<\/li>\n\n\n<li>\u0130lk olarak <code>total_exec_time<\/code> s\u0131ras\u0131na bak, toplam s\u00fcrenin y\u00fczdesini hesapla.<\/li>\n\n\n<li>\u00c7a\u011fr\u0131 say\u0131s\u0131 beklenmedik derecede y\u00fcksek sorgular\u0131 N+1 a\u00e7\u0131s\u0131ndan incele.<\/li>\n\n\n<li>Bulunan sorguyu ger\u00e7ek\u00e7i parametrelerle <code>EXPLAIN ANALYZE<\/code> ile \u00e7al\u0131\u015ft\u0131r.<\/li>\n\n\n<li>Optimizasyondan \u00f6nce istatistikleri s\u0131f\u0131rla, sonra ayn\u0131 s\u00fcre boyunca tekrar \u00f6l\u00e7.<\/li>\n\n\n<li>De\u011ferleri bir metrik sistemine aktar\u0131p trendleri izle.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Eklentinin b\u00fct\u00fcn kolonlar\u0131n\u0131n a\u00e7\u0131klamas\u0131 PostgreSQL&#8217;in <a href=\"https:\/\/www.postgresql.org\/docs\/current\/pgstatstatements.html\" target=\"_blank\" rel=\"noopener\">resmi pg_stat_statements dok\u00fcmantasyonunda<\/a> yer al\u0131yor. Kolon adlar\u0131 s\u00fcr\u00fcmler aras\u0131nda de\u011fi\u015fti\u011fi i\u00e7in, kendi s\u00fcr\u00fcm\u00fcn\u00fcze ait sayfaya bakman\u0131z\u0131 \u00f6neririm.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Performans \u00e7al\u0131\u015fmas\u0131nda en pahal\u0131 hata, yanl\u0131\u015f sorguyu optimize etmektir. pg_stat_statements, do\u011fru sorguyu bulman\u0131n en ucuz yolu.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>pg_stat_statements, PostgreSQL&#8217;de toplamda en \u00e7ok kaynak t\u00fcketen sorgular\u0131 g\u00f6sterir. Kurulum, do\u011fru s\u0131ralama, kolonlar\u0131n anlam\u0131 ve ger\u00e7ek bir \u00f6rnek.<\/p>\n","protected":false},"author":1,"featured_media":240,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-241","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-veritabani"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=241"}],"version-history":[{"count":1,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/241\/revisions"}],"predecessor-version":[{"id":281,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/241\/revisions\/281"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/240"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=241"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=241"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}