From 7da307b6f2880e6eec824b3c8ad24ce5f67263b2 Mon Sep 17 00:00:00 2001
From: Om Tita <84272601+imom29@users.noreply.github.com>
Date: Tue, 25 Nov 2025 15:19:30 +0530
Subject: [PATCH] fix: SQL Tuning Broken link (#9331)

* fix: SQL Tuning Broken link

Article mentioned in the scope is expired, this commit suggests a newer article from the same source.

* Update Link to Correctly Redirect
---
 .../system-design/content/sql-tuning@fY8zgbB13wxZ1CFtMSdZZ.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/data/roadmaps/system-design/content/sql-tuning@fY8zgbB13wxZ1CFtMSdZZ.md b/src/data/roadmaps/system-design/content/sql-tuning@fY8zgbB13wxZ1CFtMSdZZ.md
index ee10b8014..94facb921 100644
--- a/src/data/roadmaps/system-design/content/sql-tuning@fY8zgbB13wxZ1CFtMSdZZ.md
+++ b/src/data/roadmaps/system-design/content/sql-tuning@fY8zgbB13wxZ1CFtMSdZZ.md
@@ -10,5 +10,5 @@ Benchmarking and profiling might point you to the following optimizations.
 Visit the following resources to learn more:
 
 - [@official@Introduction to SQL Tuning - Oracle](https://docs.oracle.com/en/database/oracle/oracle-database/23/tgsql/introduction-to-sql-tuning.html#GUID-B653E5F3-F078-4BBC-9516-B892960046A2)
-- [@article@How we optimized PostgreSQL queries 100x](https://towardsdatascience.com/how-we-optimized-postgresql-queries-100x-ff52555eabe?gi=13caf5bcf32e)
-- [@feed@Explore top posts about SQL](https://app.daily.dev/tags/sql?ref=roadmapsh)
\ No newline at end of file
+- [@article@Query Optimization for Mere Humans in PostgreSQL](https://towardsdatascience.com/query-optimization-for-mere-humans-in-postgresql-875ab864390a/)
+- [@feed@Explore top posts about SQL](https://app.daily.dev/tags/sql?ref=roadmapsh)