<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mvcc on ads' corner</title><link>https://andreas.scherbaum.la/tags/mvcc/</link><description>Recent content in Mvcc on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Jul 2024 17:09:50 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/mvcc/index.xml" rel="self" type="application/rss+xml"/><item><title>PostgreSQL Berlin July 2024 Meetup</title><link>https://andreas.scherbaum.la/post/2024-07-17_postgresql-berlin-july-2024-meetup/</link><pubDate>Wed, 17 Jul 2024 17:09:50 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-07-17_postgresql-berlin-july-2024-meetup/</guid><description>&lt;p&gt;On July 16th, 2024, we had the &lt;em&gt;PostgreSQL&lt;/em&gt; July Meetup in &lt;em&gt;Berlin&lt;/em&gt;. &lt;em&gt;Adjust&lt;/em&gt; hosted and &lt;em&gt;Neon&lt;/em&gt; sponsored the Meetup in their &lt;em&gt;Berlin&lt;/em&gt; Headquarter at &lt;em&gt;Prenzlauer Berg&lt;/em&gt;, near the TV Tower.&lt;/p&gt;</description></item><item><title>Understanding VACUUM, VACUUM template0, and Transaction ID Wraparound</title><link>https://andreas.scherbaum.la/post/2024-06-19_understanding-vacuum-vacuum-template0-and-transaction-id-wraparound/</link><pubDate>Wed, 19 Jun 2024 18:09:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-06-19_understanding-vacuum-vacuum-template0-and-transaction-id-wraparound/</guid><description>&lt;p&gt;&lt;em&gt;PostgreSQL&lt;/em&gt; uses Multi-Version Concurrency Control (MVCC) to manage concurrent access to the database, and store each version of a tuple in a table. To keep the database efficient, &lt;em&gt;PostgreSQL&lt;/em&gt; employs a cleanup process called &lt;em&gt;VACUUM&lt;/em&gt;, which removes unnecessary tuples. This not only saves disk space and keeps the database size under control, it also prevents the dreaded &amp;ldquo;Transaction ID Wraparound&amp;rdquo; issue. Regularly running &lt;em&gt;VACUUM&lt;/em&gt; is crucial, including on the &lt;code&gt;template0&lt;/code&gt; database, which is normally handled by the &lt;em&gt;Autovacuum&lt;/em&gt; daemon. However, sometimes manual intervention is necessary.&lt;/p&gt;</description></item></channel></rss>