Re: 8.3.5 broken after power fail
От | Scott Marlowe |
---|---|
Тема | Re: 8.3.5 broken after power fail |
Дата | |
Msg-id | dcc563d10902170134p53d4a994s1f769bcb526e49e5@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 8.3.5 broken after power fail (Achilleas Mantzios <achill@matrix.gatewaynet.com>) |
Список | pgsql-admin |
2009/2/17 Achilleas Mantzios <achill@matrix.gatewaynet.com>: > Στις Tuesday 17 February 2009 10:54:52 ο/η Michael Monnerie έγραψε: > >> * your daughter with 3.5 years switching off the power supply of the >> server > 1st line of defense is to set your system to shutdown normally when the power button is pressed. > 2nd line of defense is to get your self a decent UPS unit > > My daughter does this all the time on our family FreeBSD box. No probs. > > Also at work at more than 20 tanker vessels running 7.4.2, the captains do that on a constant > basis and PgSQL always has survived (more than the rest of the system anyways..) Those are all good to have. But no UPS is a replacement for hard drives / RAID controllers / file systems that don't lie about fsync. Nothing makes your database shine like being the only one in the hosting center that survives sudden catastrophic power failure. >> What can I do? tether your daughter to the other side of the room? I'm not sure which parts of those mount options are dangerous or not. I use ext3 stock with noatime. And a battery backed RAID. Smaller slower work group / station controllers (i.e. 5 year old server conrollers) go for pretty cheap and give pretty good performance with 2 or 4 drives. AS for fixing it, I believe the answer involves creating a clog file full of zeros 16Meg or so, and pg_reset_xlog. Don't count on all your data being there or all your FK-PK type relationships to be correct, Immediately dump it, initdb and reload your data, fixing it as you go.
В списке pgsql-admin по дате отправления: