garrettmills/pg-recover
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Garrett Mills 2025-01-11 21:45:17 +00:00
parent d8455cf6a0
commit 0e1e3ada0e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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 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. 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: Requirements: