Re: postgres crash SOS
От | Dann Corbit |
---|---|
Тема | Re: postgres crash SOS |
Дата | |
Msg-id | 87F42982BF2B434F831FCEF4C45FC33E0C1E2FAE@EXCHANGE.corporate.connx.com обсуждение исходный текст |
Ответ на | Re: postgres crash SOS (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: postgres crash SOS
Re: postgres crash SOS |
Список | 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 по дате отправления: