<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>격리수준 on wid's blog</title><link>https://wid-blog.github.io/tags/%EA%B2%A9%EB%A6%AC%EC%88%98%EC%A4%80/</link><description>Recent content in 격리수준 on wid's blog</description><generator>Hugo</generator><language>ko</language><lastBuildDate>Fri, 15 Sep 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/tags/%EA%B2%A9%EB%A6%AC%EC%88%98%EC%A4%80/index.xml" rel="self" type="application/rss+xml"/><item><title>격리 수준이 실제로 막는 것</title><link>https://wid-blog.github.io/posts/tech/database/transaction-isolation-levels/</link><pubDate>Fri, 15 Sep 2023 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/posts/tech/database/transaction-isolation-levels/</guid><description>트랜잭션 격리 수준은 &amp;lsquo;어떤 이상 현상까지 허용할 것인가&amp;rsquo; 의 정책 선택이다. ANSI 4단계가 각각 막는 anomaly, 그리고 표준과 다르게 동작하는 InnoDB 의 MVCC 와 Repeatable Read.</description></item></channel></rss>