On Mon, 10 Dec 2007, Bruce Momjian wrote:
exist for disk controller caches. Consumer-grade IDE drives are
!particularly likely to have write-back caches that will not survive a
!power failure. To check write caching on Linux use
!hdparm -I; it is enabled if there is a * next
!
I thought we had the disk write cache control documented for popular
operating systems, but I see we don't so I added the following patch to
our documentation.
---
Greg Smith wrote:
> On Sat, 1 Dec 2007, Tomasz Ostrowski wro
Greg Smith wrote:
> On Mon, 10 Dec 2007, Bruce Momjian wrote:
>
> > exist for disk controller caches. Consumer-grade IDE drives are
> >!particularly likely to have write-back caches that will not survive a
> >!power failure. To check write caching on Linux use
> >!hdparm -I; it
Listaccount wrote:
Hello
I have been trapped by the advice from the manual to use "sysctl -w
vm.overcommit_memory=2" when using Linux (see 16.4.3. Linux Memory
Overcommit). This value should only be used when PostgreSQL is the only
Application running on the machine in question. It should be
