Re: 8.3.5 broken after power fail SOLVED

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I managed to recover the data that was still readable. About 650 
messageblock entries got lost. What makes me nervous a bit is that 
postgres kept running despite (partially) being destroyed. It should 
really have shutdown itself after the first problem was found. That 
database is for mails, and I would understand to have lost some from the 
time before the power loss, but I even lost entries from *after* the 
crash. That means the error happened after the system was up again and 
happily did it's work, but lost entries to a table. Could there be a 
better way to check the db at crash recovery startup time?

If someone is interested, I have a full postgres log with every single 
command done to the database.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

Attachment: signature.asc
Description: This is a digitally signed message part.


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux