| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Luke Lonergan <llonergan(at)greenplum(dot)com> |
| Cc: | Mike Biamonte <mike(at)dbeat(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Huge Data sets, simple queries |
| Date: | 2006-02-01 02:47:03 |
| Message-ID: | 20060201024703.GT95850@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jan 31, 2006 at 03:19:38PM -0800, Luke Lonergan wrote:
> > Well, the only problem with that is if the machine crashes for any
> > reason you risk having the database corrupted (or at best losing some
> > committed transactions).
>
> So, do you routinely turn off Linux write caching? If not, then there's no
> difference.
My thought was about fsync on WAL; if you're doing much writing then
a good raid write cache with BBU will improve performance.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Russell | 2006-02-01 03:14:47 | Sequential scan being used despite indexes |
| Previous Message | Luke Lonergan | 2006-02-01 01:35:32 | Re: Huge Data sets, simple queries |