| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Greg Smith" <greg(at)2ndquadrant(dot)com>, "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Tony McC" <afmcc(at)btinternet(dot)com>, "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: New server to improve performance on our large and busy DB - advice? (v2) |
| Date: | 2010-01-15 21:55:08 |
| Message-ID: | 4B508FDC020000250002E615@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> I will say that XFS seems to be a very stable file system, and we
> use it for some of our databases with no problems at all. But
> most of our stuff sits on ext3 because it's stable and reliable
> and fast enough.
Our PostgreSQL data directories are all on xfs, with everything else
(OS, etc) on ext3. We've been happy with it, as long as we turn off
write barriers, which is only save with a RAID controller with BBU
cache.
> And as always, test the crap outta your setup, cause the time to
> find problems is before you put a machine into production.
Absolutely.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2010-01-15 22:32:32 | Re: a heavy duty operation on an "unused" table kills my server |
| Previous Message | Scott Marlowe | 2010-01-15 21:42:26 | Re: new server I/O setup |