<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gorm on Vubon Notes</title><link>https://vubon.dev/tags/gorm/</link><description>Recent content in Gorm on Vubon Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 24 Jul 2026 10:00:00 +0700</lastBuildDate><atom:link href="https://vubon.dev/tags/gorm/index.xml" rel="self" type="application/rss+xml"/><item><title>Handling Postgres Locks and Connection Starvation in Go (Part 2)</title><link>https://vubon.dev/posts/postgres-connections-and-locks-part-2/</link><pubDate>Fri, 24 Jul 2026 10:00:00 +0700</pubDate><guid>https://vubon.dev/posts/postgres-connections-and-locks-part-2/</guid><description>&lt;p>In &lt;a href="https://vubon.dev/posts/postgres-connections-and-locks-part-1/">Part 1 of this series&lt;/a>, we explored how PostgreSQL manages backend processes and OS-level locking. Now, we will look at how those database-level locks interact with an application&amp;rsquo;s connection pool, causing connection starvation, and how to elegantly mitigate these issues in Go using GORM.&lt;/p></description></item></channel></rss>