Re: postgres crash SOS - Mailing list pgsql-general

From Dann Corbit
Subject Re: postgres crash SOS
Date
Msg-id 87F42982BF2B434F831FCEF4C45FC33E0C1E2FAE@EXCHANGE.corporate.connx.com
Whole thread Raw
In response to Re: postgres crash SOS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: postgres crash SOS  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: postgres crash SOS  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Thursday, June 17, 2010 12:20 PM
> To: Dann Corbit
> Cc: Felde Norbert; pgsql-general@postgresql.org; Scott Marlowe
> Subject: Re: [GENERAL] postgres crash SOS
>
> Dann Corbit <DCorbit@connx.com> writes:
> >> (Personally I'd never run a database I cared about on Windows.)
>
> > Somehow, I doubt that Windows is to blame.  For instance, Oracle and
> SQL*Server seem to run fine on Windows without this sort of problem.
>
> Really?  Are you front-line support for either, so that you can say
> that they "never" have this sort of problem on the basis of any actual
> evidence?  Our failure rate on Windows is probably pretty low too,
> it's just that we only hear about non-working cases here.

I have worked as a DBA for large farms of database systems.

> (Perhaps more to the point, if they don't have problems, it's likely
> because they tell their customers how to configure Windows boxes safely
> before the fact.  And people who are spending the money for an Oracle
> license will heed that advice.)
>

Care was taken in selection of hardware and configuration.  Is this different for any database system?


pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: postgres crash SOS
Next
From: "Joshua D. Drake"
Date:
Subject: Re: postgres crash SOS