{"id":81,"date":"2026-09-29T17:40:00","date_gmt":"2026-09-29T17:40:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/29\/transaction-isolation-levels-read-committed\/"},"modified":"2026-09-29T17:40:00","modified_gmt":"2026-09-29T17:40:00","slug":"transaction-isolation-levels-read-committed","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/09\/29\/transaction-isolation-levels-read-committed\/","title":{"rendered":"Read Committed Size Ne S\u00f6z Veriyor? Transaction Isolation Seviyeleri"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">\u00c7o\u011fu backend geli\u015ftiricisi i\u00e7in transaction \u015fu anlama gelir:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ya hepsi olur ya hi\u00e7biri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu do\u011fru. Atomiklik transaction&#8217;\u0131n en bilinen \u00f6zelli\u011fi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama transaction&#8217;\u0131n daha az konu\u015fulan bir yan\u0131 var: ayn\u0131 anda \u00e7al\u0131\u015fan di\u011fer transaction&#8217;lar\u0131 ne kadar g\u00f6rd\u00fc\u011f\u00fc.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bunu isolation seviyesi belirler ve \u00e7o\u011fu uygulama hangi seviyede \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 bilmeden \u00e7al\u0131\u015f\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Varsay\u0131lan de\u011fer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PostgreSQL, SQL Server ve Oracle&#8217;da varsay\u0131lan seviye <code>READ COMMITTED<\/code>. MySQL InnoDB&#8217;de ise <code>REPEATABLE READ<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Yani ayn\u0131 kod, farkl\u0131 veritabanlar\u0131nda farkl\u0131 e\u015fzamanl\u0131l\u0131k davran\u0131\u015f\u0131 g\u00f6sterebilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Read committed neyi garanti eder?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Read committed tek bir \u015fey s\u00f6z verir: commit edilmemi\u015f veriyi g\u00f6rmezsiniz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ba\u015fka bir transaction&#8217;\u0131n yar\u0131da kalm\u0131\u015f de\u011fi\u015fikliklerini okumazs\u0131n\u0131z. Bu iyi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama ayn\u0131 transaction i\u00e7inde ayn\u0131 sorguyu iki kez \u00e7al\u0131\u015ft\u0131r\u0131rsan\u0131z farkl\u0131 sonu\u00e7 alabilirsiniz:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>BEGIN;\nSELECT balance FROM accounts WHERE id = 1;  -- 500\n-- bu arada ba\u015fka bir transaction commit etti\nSELECT balance FROM accounts WHERE id = 1;  -- 300\nCOMMIT;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Her sorgu, o sorgunun ba\u015flad\u0131\u011f\u0131 andaki commit edilmi\u015f veriyi g\u00f6r\u00fcr. Transaction&#8217;\u0131n ba\u015flad\u0131\u011f\u0131 an\u0131 de\u011fil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir raporda \u00f6nce toplam\u0131, sonra detaylar\u0131 okuyorsan\u0131z, ikisi birbiriyle tutars\u0131z olabilir. Toplam 1000 der, detaylar\u0131n toplam\u0131 1200 eder.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Read-modify-write<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As\u0131l tehlike \u015fu kal\u0131pta ortaya \u00e7\u0131kar:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>BEGIN;\nSELECT stock FROM products WHERE id = 7;   -- 1\n-- uygulama: stok varsa sat\nUPDATE products SET stock = 0 WHERE id = 7;\nINSERT INTO orders ...;\nCOMMIT;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130ki transaction ayn\u0131 anda \u00e7al\u0131\u015f\u0131rsa ikisi de sto\u011fu 1 olarak okur. \u0130kisi de sat\u0131\u015f yapar. Tek \u00fcr\u00fcn iki kez sat\u0131lm\u0131\u015f olur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Transaction kullan\u0131lm\u0131\u015f. Hatas\u0131z commit olmu\u015f. Ama sonu\u00e7 yanl\u0131\u015f.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Read committed bu durumu engellemez. Bunu engellemek i\u00e7in ya sat\u0131r okunurken kilitlenmeli:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>SELECT stock FROM products WHERE id = 7 FOR UPDATE;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">ya da kontrol ve g\u00fcncelleme tek bir atomik sorguda yap\u0131lmal\u0131:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>UPDATE products SET stock = stock - 1\nWHERE id = 7 AND stock &gt; 0;<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Repeatable read<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu seviyede transaction, ba\u015flad\u0131\u011f\u0131 andaki veritaban\u0131n\u0131n bir anl\u0131k g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc g\u00f6r\u00fcr. Ayn\u0131 sorgu transaction boyunca hep ayn\u0131 sonucu verir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rapor tutars\u0131zl\u0131\u011f\u0131 problemi \u00e7\u00f6z\u00fcl\u00fcr.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PostgreSQL&#8217;de bu seviyede iki transaction ayn\u0131 sat\u0131r\u0131 g\u00fcncellemeye \u00e7al\u0131\u015f\u0131rsa ikincisi hata al\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ERROR: could not serialize access due to concurrent update<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Bu bir bug de\u011fil, bir korumad\u0131r. Uygulaman\u0131n bu hatay\u0131 yakalay\u0131p transaction&#8217;\u0131 ba\u015ftan denemesi gerekir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama repeatable read bile her anomaliyi engellemez. Write skew denen durumda iki transaction farkl\u0131 sat\u0131rlara yazar, ama her biri di\u011ferinin okudu\u011fu veriye dayanarak karar vermi\u015ftir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Klasik \u00f6rnek: n\u00f6bet\u00e7i doktor sistemi. Kural &#8220;en az bir doktor n\u00f6bette olmal\u0131&#8221;. \u0130ki doktor ayn\u0131 anda n\u00f6betten \u00e7\u0131kmak ister. \u0130kisi de di\u011ferinin n\u00f6bette oldu\u011funu g\u00f6r\u00fcr ve kendi kayd\u0131n\u0131 g\u00fcnceller. Sonu\u00e7ta kimse n\u00f6bette kalmaz.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Serializable<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">En g\u00fc\u00e7l\u00fc seviye. Sonu\u00e7, transaction&#8217;lar s\u0131rayla \u00e7al\u0131\u015fm\u0131\u015f gibi olmak zorundad\u0131r. Write skew dahil anomaliler engellenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">PostgreSQL bunu kilitlerle de\u011fil, \u00e7ak\u0131\u015fmalar\u0131 tespit ederek yapar. \u00c7ak\u0131\u015fma olursa transaction&#8217;lardan biri serialization hatas\u0131 al\u0131r ve tekrar denenmelidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bedeli daha fazla retry ve bir miktar performans kayb\u0131d\u0131r. Ama bir\u00e7ok uygulama i\u00e7in tahmin edildi\u011fi kadar y\u00fcksek de\u011fildir. Kritik i\u015flemler i\u00e7in do\u011fru seviyeyi se\u00e7mek, her yere manuel kilit eklemekten daha g\u00fcvenli olabilir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Pratikte ne yap\u0131yorum?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Varsay\u0131lan read committed ile \u00e7al\u0131\u015f\u0131p kritik noktalarda a\u00e7\u0131k kararlar veriyorum:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Okuyup sonra yazan i\u015f mant\u0131\u011f\u0131nda ya <code>FOR UPDATE<\/code> ya da atomik g\u00fcncelleme.<\/li>\n\n\n<li>Tutarl\u0131 g\u00f6r\u00fcnt\u00fc gereken raporlarda repeatable read.<\/li>\n\n\n<li>Kurallar\u0131 birden fazla sat\u0131ra yay\u0131lan ve hata maliyeti y\u00fcksek i\u015flemlerde serializable ve retry.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ve en \u00f6nemlisi, hangi seviyede \u00e7al\u0131\u015ft\u0131\u011f\u0131m\u0131z\u0131 bilmek.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Transaction kullanmak g\u00fcvenli oldu\u011fumuz hissini veriyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama hangi garantiyi ald\u0131\u011f\u0131m\u0131z\u0131 bilmeden kullan\u0131lan transaction, sadece daha d\u00fczenli g\u00f6r\u00fcnen bir race condition.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Transaction kullanmak her e\u015fzamanl\u0131l\u0131k problemini \u00e7\u00f6zmez. Read committed, repeatable read ve serializable seviyelerinin pratikte neyi engelledi\u011fi, neyi engellemedi\u011fi.<\/p>\n","protected":false},"author":1,"featured_media":80,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-81","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\/81","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=81"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/81\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/80"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=81"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=81"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=81"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}