<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Connection Pools on Nalar</title>
    <link>https://nalar.dev/tags/connection-pools/</link>
    <description>Recent content in Connection Pools on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/connection-pools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Connection Pools Turn Session State Into Shared State</title>
      <link>https://nalar.dev/connection-pools-turn-session-state-into-shared-state/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/connection-pools-turn-session-state-into-shared-state/</guid>
      <description>&lt;p&gt;A database connection pool reuses physical sessions across many logical borrowers. That reuse changes the lifetime of session-scoped state. A setting applied by one request can outlive the request itself because returning a connection to the pool usually ends only the borrower&amp;rsquo;s access to that connection, not the database session behind it.&lt;/p&gt;&#xA;&lt;p&gt;This distinction matters whenever application code changes properties that belong to the session rather than to a single statement or transaction. Transaction isolation, read-only mode, schema selection, session variables, advisory locks, temporary objects, prepared statements, and database-specific configuration can all have lifetimes that differ from the lexical scope of application code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
