From 0e1e3ada0e48012c3f160ca241a9eaf9db5ed502 Mon Sep 17 00:00:00 2001 From: Garrett Mills Date: Sat, 11 Jan 2025 21:45:17 +0000 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cc1ece7..795b01a 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ BUT good physical disks (say after an unclean exit, or you've snapshotted bad di them on a good server). It does this by creating a clean "recovery" table with the same schema and reading rows from the bad table one at a time, skipping rows and blocks with bad disk errors. -For more specifics on how this works technically, see my blog post. +For more specifics on how this works technically, see [my blog post](https://garrettmills.dev/blog/2025/01/11/Salvaging-a-Corrupted-Table-from-PostgreSQL/). Requirements: