This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
how_to:database_issues [2013/08/30 12:34] – [Database Issues] paul | how_to:database_issues [2013/08/30 12:35] – paul | ||
---|---|---|---|
Line 5: | Line 5: | ||
* [[Database & Disk Caching]] | * [[Database & Disk Caching]] | ||
- | =====Disk Caching===== | ||
- | One key point is that, like all other high-end databases, PostgreSQL should not be run on a server with disk level [[http:// | ||
- | |||
- | High-end RAID controllers often contain a battery backed write cache (BBWC) - in this case, if the power fails, the cached data is held in battery powered memory until the power is restored. After power is restored the cached data will be written to disk. In this case, using write back caching through the BBWC is perfectly safe (as long as power is not left off for so long that the batteries run down). | ||
- | |||
- | It is slightly less safe, but still usually OK, to have a UPS with automated shutdown of the PC. You still have to ensure that the PC is not just turned off without shutting down properly. | ||
- | |||
- | If you don't have either of these facilities, then make sure you turn off write-back caching in Windows. (Note that ' | ||
- | |||
- | Exactly how you turn off write-back caching depends on your version of Windows, and the disk controller. | ||
- | |||
- | The instructions below are for Windows 7 with standard SATA disks | ||
- | |||
- | - Go to the ' | ||
- | - Under **Disk Drives** find the hard disk that VPOP3 is installed on, and right-click it and choose **Properties**\\ {{: | ||
- | - Go to the **Policies** tab. Turn off **Enable write caching onthe device** and press **OK**\\ {{: | ||
=====Possible Conflicting Software===== | =====Possible Conflicting Software===== |