| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Chen, Dongdong (GE Healthcare)" <DongdongChen(at)ge(dot)com> |
| Cc: | jd(at)commandprompt(dot)com, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: need help for PostgreSQL consistency check mechanism |
| Date: | 2009-04-24 02:28:43 |
| Message-ID: | dcc563d10904231928l1e1ef555oba62c63ae9349e11@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 23, 2009 at 8:24 PM, Chen, Dongdong (GE Healthcare)
<DongdongChen(at)ge(dot)com> wrote:
> I wanna know if there is any way or tool to detect the DB data loss or
> damage and inform developer the result before recovery? If there is
> data loss, the DB could still open or not ?
> Sometimes even if shutdown abnormally, the data still keep in good
> condition.
Assuming non broken hardware and a drive subsystem that doesn't lie
about fsync, and that the dba hasn't turned off fsync, an abnormal
shutdown should NEVER result in a corrupted database.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dennis Gearon | 2009-04-24 04:53:19 | feature suggestion and return to pgsql-general :-) |
| Previous Message | Chen, Dongdong (GE Healthcare) | 2009-04-24 02:24:11 | Re: need help for PostgreSQL consistency check mechanism |