| From: | "Welty, Richard" <richard(dot)welty(at)bankofamerica(dot)com> |
|---|---|
| To: | Gregory Youngblood <pgcluster(at)netio(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Why database is corrupted after re-booting |
| Date: | 2005-10-26 16:40:53 |
| Message-ID: | A209FE4DA934614CAF3F5BD8E5E14290B0DEC1@ex2k.bankofamerica.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Gregory Youngblood wrote:
>Is corruption a problem? I don't think so - but I want to make sure I haven't had my
>head in the sand for a while. :) I realize this instance appears to be on Windows,
>which is relatively new as a native Windows program. I'm really after the answer on
>more mature platforms (including Linux).
crappy disk drives and bad windows file systems, nothing more. postgresql is
rather corruption free when the surrounding hardware and software environments
are well chosen.
if you do have to use cheap disk drives/controllers, then a battery backup
unit that shuts the server down automagically is a really really good idea.
getting that IDE cache flushed is pretty high on the priority list.
richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-10-26 16:50:07 | Re: Why database is corrupted after re-booting |
| Previous Message | Troy | 2005-10-26 16:30:07 | Re: Why database is corrupted after re-booting |