<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Database Tuning on The Coders Blog</title><link>https://thecodersblog.com/tag/database-tuning/</link><description>Recent content in Database Tuning on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Apr 2026 16:57:18 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/database-tuning/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux 7.0: How a Kernel Preemption Bug Crippled PostgreSQL Performance in 2026</title><link>https://thecodersblog.com/linux-kernel-7-0-preemption-regression-impact-on-postgresql-2026/</link><pubDate>Wed, 29 Apr 2026 16:57:18 +0000</pubDate><guid>https://thecodersblog.com/linux-kernel-7-0-preemption-regression-impact-on-postgresql-2026/</guid><description>&lt;p&gt;In April 2026, the Linux Kernel 7.0 release promised evolutionary advancements, but for PostgreSQL users, it delivered a brutal, silent performance regression, abruptly halving throughput on critical production workloads without a single error message.&lt;/p&gt;
&lt;h2 id="the-silent-killer-how-linux-70-blindfolded-postgresql"&gt;The Silent Killer: How Linux 7.0 Blindfolded PostgreSQL&lt;/h2&gt;
&lt;p&gt;The eagerly awaited release of Linux Kernel 7.0 in early 2026 was met with the usual anticipation within the open-source community. Touted for its efficiency improvements and new hardware support, it was expected to be a solid, if not revolutionary, upgrade. Yet, for database administrators and cloud engineers managing high-performance PostgreSQL instances, it brought an unforeseen and devastating impact.&lt;/p&gt;</description></item></channel></rss>