Update README.md
This commit is contained in:
parent
d8455cf6a0
commit
0e1e3ada0e
@ -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:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user