From: | Dann Corbit <DCorbit(at)connx(dot)com> |
---|---|
To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Felde Norbert <fenor77(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Subject: | Re: postgres crash SOS |
Date: | 2010-06-17 19:27:44 |
Message-ID: | 87F42982BF2B434F831FCEF4C45FC33E0C1E2FAE@EXCHANGE.corporate.connx.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Thursday, June 17, 2010 12:20 PM
> To: Dann Corbit
> Cc: Felde Norbert; pgsql-general(at)postgresql(dot)org; Scott Marlowe
> Subject: Re: [GENERAL] postgres crash SOS
>
> Dann Corbit <DCorbit(at)connx(dot)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?
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2010-06-17 19:42:01 | Re: postgres crash SOS |
Previous Message | Scott Marlowe | 2010-06-17 19:22:09 | Re: postgres crash SOS |