Re: Database integrity and disaster recovery
От | Tom Lane |
---|---|
Тема | Re: Database integrity and disaster recovery |
Дата | |
Msg-id | 21696.966658331@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Database integrity and disaster recovery (Martin Christensen <knightsofspamalot-factotum@mail1.stofanet.dk>) |
Список | pgsql-general |
Martin Christensen <knightsofspamalot-factotum@mail1.stofanet.dk> writes: > I've heard some rumours off Slashdot that PostgreSQL databases tend to > corrupt more than, say, MySQL, and that disaster recovery is more > difficult. The MySQL people assert that, but their objectivity is, um, suspect. I don't think I've heard any such claim from an independent third party. I've heard of very few cases of actual data corruption in Postgres databases --- and several of the ones I have seen personally were eventually traced to flaky disk or disk-controller hardware, not software faults. We have had some problems with index corruption (although those bugs are progressively getting cleaned out), but the basic table format is mighty simple and hard to do much damage to. Recovery from a corrupted index on a user table is pretty easy: drop and recreate the index. Corrupted system indexes are nastier, since dropping them may disable normal database operations entirely. Beginning in 7.0 there is a REINDEX command that you can invoke in standalone mode if you find yourself in that position. It's a pretty rare problem, however. regards, tom lane
В списке pgsql-general по дате отправления: