| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Curt Sampson <cjs(at)cynic(dot)net> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] O_DIRECT for WAL writes |
| Date: | 2005-06-23 03:51:34 |
| Message-ID: | 389.1119498694@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Curt Sampson <cjs(at)cynic(dot)net> writes:
> But regardless, perhaps we can add some stuff to the various OSes'
> startup scripts that could help with this. For example, in NetBSD you
> can "dkctl <device> setcache r" for most any disk device (certainly all
> SCSI and ATA) to enable the read cache and disable the write cache.
[ shudder ] I can see the complaints now: "Merely starting up Postgres
cut my overall system performance by a factor of 10! I wasn't even
using it!! What a piece of junk!!!" I can hardly think of a better
way to drive away people with a marginal interest in the database...
This can *not* be default behavior, and unfortunately that limits its
value quite a lot.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curt Sampson | 2005-06-23 03:54:15 | Re: [PATCHES] O_DIRECT for WAL writes |
| Previous Message | Curt Sampson | 2005-06-23 03:14:07 | Re: [PATCHES] O_DIRECT for WAL writes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curt Sampson | 2005-06-23 03:54:15 | Re: [PATCHES] O_DIRECT for WAL writes |
| Previous Message | Curt Sampson | 2005-06-23 03:14:07 | Re: [PATCHES] O_DIRECT for WAL writes |