| From: | "Mendola Gaetano" <mendola(at)bigfoot(dot)com> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <Alex(dot)H(dot)Pollock(at)WellsFargo(dot)COM> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Diagnose Database Corruption |
| Date: | 2003-06-09 10:56:34 |
| Message-ID: | 000a01c32e75$cbfe7c50$10d4a8c0@mm.eutelsat.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> We don't have a checker because if it is corrupt, it will mention
> something in the server logs or correct it automatically. Corruption is
> very rare, usually hardware flakiness.
I agree about the fact that corruption is very rare but sometimes I got
a "duplicate primary key" and the only solution was dump the DB,
edit the dump and restore the DB.
If the dump is uge ( like 400 MB ) is a lot of down time :-(
The problem disappeared after removing the reindex on that table
scheduled each morning.
Regards
Gaetano Mendola.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mendola Gaetano | 2003-06-09 11:03:30 | Re: What could be the problem? |
| Previous Message | Bruce Momjian | 2003-06-09 01:21:56 | Re: Diagnose Database Corruption |