<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Introduction on sharedbuffers</title><link>https://sharedbuffers.com.br/en/tags/introduction/</link><description>Recent content in Introduction on sharedbuffers</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sharedbuffers.com.br/en/tags/introduction/index.xml" rel="self" type="application/rss+xml"/><item><title>sharedbuffers: knowledge that doesn't get lost on disk</title><link>https://sharedbuffers.com.br/en/posts/what-is-shared-buffers/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://sharedbuffers.com.br/en/posts/what-is-shared-buffers/</guid><description>&lt;p&gt;In PostgreSQL, &lt;code&gt;shared_buffers&lt;/code&gt; is the parameter that defines the size of the buffer pool — the memory area where data pages are kept warm so queries don&amp;rsquo;t need to hit the disk on every access.&lt;/p&gt;
&lt;p&gt;When a page is in the buffer, it&amp;rsquo;s immediately available to any database process. That&amp;rsquo;s the point: &lt;strong&gt;shared memory that speeds everything up&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;This blog&amp;rsquo;s name comes from that, but the metaphor goes a bit further than the parameter.&lt;/p&gt;</description></item></channel></rss>