| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange nbtree corruption report |
| Date: | 2011-11-29 01:07:28 |
| Message-ID: | A3C798C4-998C-489C-B438-FB338F3ABAF9@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 28, 2011, at 3:44 PM, Alvaro Herrera wrote:
> I wonder if it would be worthwhile to build some sort of tool to scan
> the heap and ensure that there are index entries for all heap items,
> just to test the hypothesis. Not that this would enlighten on the
> source of the actual problem.
There was a project to create a sanity-checker for Postgres databases... did that ever go anywhere? It seems like this would be a good addition for that tool, if it exists.
In either case, I am all for better capabilities to detect data problems (I'm looking at you, block checksum project! ;)
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-11-29 01:11:09 | Re: strange nbtree corruption report |
| Previous Message | Nathan Wagner | 2011-11-28 22:12:20 | Re: psql line number reporting from stdin |