<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deep Dive on ilikeorangutans</title><link>https://kuelzer.ca/tags/deep-dive/</link><description>Recent content in Deep Dive on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Sun, 03 May 2026 12:37:51 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/deep-dive/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres Structure and Query Deep Dive</title><link>https://kuelzer.ca/posts/2026/05/02/postgres-structure-and-query-deep-dive/</link><pubDate>Sat, 02 May 2026 14:23:40 -0400</pubDate><guid>https://kuelzer.ca/posts/2026/05/02/postgres-structure-and-query-deep-dive/</guid><description>&lt;p&gt;In an effort to understand Postgres better I&amp;rsquo;ve worked my way through how a Postgres database is structured and executes queries.&lt;/p&gt;
&lt;h2 id="process-model"&gt;Process Model&lt;/h2&gt;
&lt;p&gt;Postgres uses a process-per-worker model. That means every connection is handled by a separate operating system process forked off the initial process.&lt;/p&gt;
&lt;h2 id="subsystem-overview"&gt;Subsystem Overview&lt;/h2&gt;
&lt;p&gt;Postgres consists of several components that all work together to process data and ensure it&amp;rsquo;s reliably written and can be looked up efficiently. The following are the most important components, but there more, other components that are beyond the scope of this post.&lt;/p&gt;</description></item></channel></rss>