| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amir Becher <abecher(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Corrupt index |
| Date: | 2003-04-10 20:55:51 |
| Message-ID: | 6641.1050008151@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Amir Becher <abecher(at)yahoo(dot)com> writes:
> The source of the problem was the VERITAS Backup Exec.
> I was able to replicate the index corruption in under
> a minute by running a backup and updating the database
> at the same time.
Fascinating. It would be interesting to know exactly what Veritas is
doing that causes the problem. Do any error messages show up in the
postmaster log while you are doing the above?
I'm still quite concerned about the health of your database, btw.
I can't see any reason to think that whatever interference is going
on would corrupt only indexes. There may be problems accumulating
in the table files as well :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amir Becher | 2003-04-10 21:44:12 | Re: Corrupt index |
| Previous Message | Camarao, Wagner (v) | 2003-04-10 20:54:39 | (mysql to postgresql) in php functions |