<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Farolan Faisal</title><description>I work on PostgreSQL performance and the systems around it — finding why a query costs what it costs, fixing it, and shipping the fix.</description><link>https://farol.dev/</link><item><title>A benchmark with no network in it measures the floor</title><link>https://farol.dev/blog/a-benchmark-that-understates-the-problem/</link><guid isPermaLink="true">https://farol.dev/blog/a-benchmark-that-understates-the-problem/</guid><description>A cascade delete that took seven minutes in production is a barely-visible win on my laptop. Measuring the per-statement cost showed why, and why a local number here is a floor rather than the size of the fix.</description><pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate><category>postgres</category></item><item><title>An array parameter of the wrong width</title><link>https://farol.dev/blog/an-array-parameter-of-the-wrong-width/</link><guid isPermaLink="true">https://farol.dev/blog/an-array-parameter-of-the-wrong-width/</guid><description>The same id list, one type wider than the column, costs two hundred times as much. PostgreSQL explains both statements with the identical plan, and EXPLAIN reports the same buffers.</description><pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate><category>postgres</category></item></channel></rss>