Re: Why database is corrupted after re-booting - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Why database is corrupted after re-booting
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE92E7CF@algol.sollentuna.se
Whole thread Raw
In response to Why database is corrupted after re-booting  ("Andrus" <eetasoft@online.ee>)
List pgsql-general
> 1. Windows XP
> 2. QUANTUM FIREBALLP LM20.5  (IDE drive)
> 3. Write caching is off in XP device manager
> 4. fsync is ON in Postgres 8

Coming late into the discussion, there is one more note I'd add to this
- if you're on windows and want to be extra secure, also set
wal_sync_method=fsync_writethrough. This will get it through most (I
would say all if I was sure, but I'm not) IDE disks that lie about write
completion.

//Magnus

pgsql-general by date:

Previous
From: John Sidney-Woollett
Date:
Subject: Re: Please HELP - URGENT - transaction wraparound error
Next
From: David Eduardo Gómez Noguera
Date:
Subject: Re: querying while copying into a table and optimizations