Re: best OS and HW for postgreSQL - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: best OS and HW for postgreSQL
Date
Msg-id 1159201478.26848.15.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: best OS and HW for postgreSQL  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: best OS and HW for postgreSQL  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-admin
On Mon, 2006-09-25 at 10:28, Joshua D. Drake wrote:
> Scott Marlowe wrote:
> > On Sun, 2006-09-24 at 20:18 -0400, Jim Nasby wrote:
> >> On Sep 22, 2006, at 6:12 PM, Raul Retamozo wrote:
> >>> Hi everyone on the list. I want to know what is the reccommended OS
> >>> to work with PostgreSQL , on specific with PostGIS:
> >>> One more question is about what HW (server) offers the best
> >>> performance for a Web Map Server bases on PostGIS and mapserver.
> >> In general, you're probably best off running whatever OS you're most
> >> comfortable with.
> >
> > I'd amend that to say whatever flavor of unix you're most comfortable
> > with.
>
> Well honestly that isn't true either. Linux is faster then Solaris for
> PostgreSQL in a lot of cases. In reality... I would say the best OS for
> PostgreSQL is either Linux or FreeBSD. Win32 is great for a small
> installation or development.
>
> The Solaris argument may change for 8.2, I don't know.

Seems the same thing is true for other databases (the one that cannot be
named comes to mind).

> >
> > Much more important is your disk subsystem.  Using an Areca RAID
> > controller with battery backed cache and a half dozen or more hard
> > drives is often the real winner for performance.
>
> Yes, LSI and 3Ware are also good. I am particularly fond of LSI but
> Areca has PCI-Express cards which means you can put them on cheaper
> motherboards :)

I too have a soft spot in my heart for LSI MegaRAID cards.  They've
never treated me badly.

pgsql-admin by date:

Previous
From: Srinivas Lakshmi Sistla
Date:
Subject: postgrses database problem
Next
From: Scott Marlowe
Date:
Subject: Re: postgrses database problem