| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dann Corbit <DCorbit(at)connx(dot)com> |
| 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:19:57 |
| Message-ID: | 24263.1276802397@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
(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.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2010-06-17 19:22:09 | Re: postgres crash SOS |
| Previous Message | Dann Corbit | 2010-06-17 19:06:14 | Re: postgres crash SOS |