[{"content":"In PostgreSQL, shared_buffers is the parameter that defines the size of the buffer pool — the memory area where data pages are kept warm so queries don\u0026rsquo;t need to hit the disk on every access.\nWhen a page is in the buffer, it\u0026rsquo;s immediately available to any database process. That\u0026rsquo;s the point: shared memory that speeds everything up.\nThis blog\u0026rsquo;s name comes from that, but the metaphor goes a bit further than the parameter.\nWhat sharedbuffers is sharedbuffers is a blog about PostgreSQL. Not about PostgreSQL in general — about the PostgreSQL you run in production, that you need to tune when latency spikes at 3am, that you need to understand deeply when a client asks why a query that worked yesterday suddenly doesn\u0026rsquo;t.\nThe name is a double reference: to the shared_buffers parameter, and to the idea of shared knowledge. A buffer of experience that doesn\u0026rsquo;t need to be reloaded from scratch every time.\nWho this blog is for For people who work with PostgreSQL and want to go beyond SELECT * FROM. For DBAs who already know what an index is but want to understand when not to create one. For developers who noticed a slow query and need to know where to start. For sysadmins who need to configure a PostgreSQL server deliberately, not by guesswork.\nWe won\u0026rsquo;t cover the basics by design. The assumption here is that you already have PostgreSQL running and want to understand what\u0026rsquo;s happening underneath.\nWhat you\u0026rsquo;ll find here Memory tuning and parameter configuration. Query plan analysis — the EXPLAIN ANALYZE outputs that reveal what the planner was actually thinking. Backup strategies, replication, high availability.\nAll with real examples — queries you can run on your own database right now and compare with what you find here.\nWhere it makes sense, each post will have a Portuguese version too, since most of this content is also written for the Brazilian PostgreSQL community.\nAbout sharedbuffers This blog is maintained by people who work with PostgreSQL in production every day. The idea was straightforward from the start: write down what we learn before it gets lost in the daily grind — and share it with people dealing with the same problems.\nEnjoy.\n","permalink":"https://sharedbuffers.com.br/en/posts/what-is-shared-buffers/","summary":"\u003cp\u003eIn PostgreSQL, \u003ccode\u003eshared_buffers\u003c/code\u003e is the parameter that defines the size of the buffer pool — the memory area where data pages are kept warm so queries don\u0026rsquo;t need to hit the disk on every access.\u003c/p\u003e\n\u003cp\u003eWhen a page is in the buffer, it\u0026rsquo;s immediately available to any database process. That\u0026rsquo;s the point: \u003cstrong\u003eshared memory that speeds everything up\u003c/strong\u003e.\u003c/p\u003e\n\u003cp\u003eThis blog\u0026rsquo;s name comes from that, but the metaphor goes a bit further than the parameter.\u003c/p\u003e","title":"sharedbuffers: knowledge that doesn't get lost on disk"},{"content":"sharedbuffers is a technical blog about PostgreSQL.\nThe idea is to gather in one place the knowledge earned through practice — on production servers, during 3am incidents, in major version upgrades nobody wanted to tackle. Memory tuning, query plans, backup strategies, replication, high availability — with real examples, no fluff.\nThe content is written by people who work with PostgreSQL in critical production environments every day. Each post comes from real situations, not from re-reading the docs.\nGot a topic suggestion or just want to talk PostgreSQL? We\u0026rsquo;d love to hear from you.\n","permalink":"https://sharedbuffers.com.br/en/about/","summary":"\u003cp\u003e\u003cstrong\u003esharedbuffers\u003c/strong\u003e is a technical blog about PostgreSQL.\u003c/p\u003e\n\u003cp\u003eThe idea is to gather in one place the knowledge earned through practice — on production servers, during 3am incidents, in major version upgrades nobody wanted to tackle. Memory tuning, query plans, backup strategies, replication, high availability — with real examples, no fluff.\u003c/p\u003e\n\u003cp\u003eThe content is written by people who work with PostgreSQL in critical production environments every day. Each post comes from real situations, not from re-reading the docs.\u003c/p\u003e","title":"About"}]