<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database on ads' corner</title><link>https://andreas.scherbaum.la/tags/database/</link><description>Recent content in Database on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Jun 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/database/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres Extensions Day Montréal 2025</title><link>https://andreas.scherbaum.la/post/2025-06-02_postgres-extensions-day-montreal-2025/</link><pubDate>Mon, 02 Jun 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-06-02_postgres-extensions-day-montreal-2025/</guid><description>&lt;p&gt;On Monday before PGConf.dev, the &lt;a href="https://pgext.day/"&gt;Postgres Extensions Day 2025&lt;/a&gt; took place. Same venue, same floor. A day fully packed with talks, and interesting discussions.&lt;/p&gt;&#10;&lt;p&gt;This event shows once again that extensions in &lt;em&gt;PostgreSQL&lt;/em&gt; are thriving. It also shows that there is a lot of work to do to make extensions more usable and discoverable for users. Just a few problems which where discussed:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;A database can only load one extension version.&lt;/li&gt;&#10;&lt;li&gt;Installing a new version of an extension without upgrading all databases may or may not work: depends if the library is backwards compatible.&lt;/li&gt;&#10;&lt;li&gt;Rolling forward to a new version usually works, rolling backwardsis complicated or impossible.&lt;/li&gt;&#10;&lt;li&gt;Restoring a backup with an older version of an extension might not work.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;The event was organized by &lt;a href="https://postgresql.life/post/yurii_rashkovskii/" title="PostgreSQL Person of the Week interview with: Yurii Rashkovskii"&gt;Yurii Rashkovskii&lt;/a&gt; and &lt;a href="https://postgresql.life/post/chris_travers/" title="PostgreSQL Person of the Week interview with: Chris Travers"&gt;Chris Travers&lt;/a&gt; (who could not attend).&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><item><title>PostgreSQL Development Conference 2024 - Review</title><link>https://andreas.scherbaum.la/post/2024-06-14_postgresql-development-conference-2024-review/</link><pubDate>Fri, 14 Jun 2024 02:00:25 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2024-06-14_postgresql-development-conference-2024-review/</guid><description>&lt;p&gt;This year&amp;rsquo;s &lt;em&gt;PGCon&lt;/em&gt; was different. For starters, the conference is renamed to &lt;em&gt;PGConf.dev&lt;/em&gt;, and it no longer takes place in &lt;em&gt;Ottawa&lt;/em&gt;, but in &lt;em&gt;Vancouver, BC&lt;/em&gt;. It&amp;rsquo;s also a new team which organized the conference, and they did a superb job!&lt;/p&gt;</description></item></channel></rss>