<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>db-optimization on Dhaval Shah</title><link>https://www.dhaval-shah.com/tags/db-optimization/</link><description>Recent content in db-optimization on Dhaval Shah</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Mon, 06 Jul 2026 01:00:50 +0000</lastBuildDate><atom:link href="https://www.dhaval-shah.com/tags/db-optimization/index.xml" rel="self" type="application/rss+xml"/><item><title>Same JSON Storage Problem, Different Database - What Postgres Does Differently</title><link>https://www.dhaval-shah.com/db-optimization-ai-review/</link><pubDate>Mon, 06 Jul 2026 01:00:50 +0000</pubDate><guid>https://www.dhaval-shah.com/db-optimization-ai-review/</guid><description>Background My earlier article on AI augmented Fintech post-mortem review walked through an Oracle JSON storage problem: a payment transaction table stored as JSON, a query that needed to filter on a nested field, and the chain of fixes - that the team eventually needed.
Out of curiosity - a reasonable question came out of that post: does Postgres have the same problem?
The honest answer is partly yes, partly no.</description></item></channel></rss>