| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First-draft release notes for next week's releases |
| Date: | 2014-03-19 20:55:22 |
| Message-ID: | 8829.1395262522@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> So, I'll ask again (because I didn't see a reply): is there any way
> users can *check* if they've been corrupted? Short of waiting for PK/FK
> violations?
I think it would work to do a REINDEX on each table (doesn't matter which
index you select) and see if it complains about not being able to find any
parent tuples. This would definitely catch the case as long as the
orphaned HOT tuple is still live. If it's not, the immediate problem is
gone ... but it's still possible you have follow-on corruption.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-03-19 21:01:33 | Re: First-draft release notes for next week's releases |
| Previous Message | Josh Berkus | 2014-03-19 20:51:05 | Re: [HACKERS] First draft of update announcement |