Re: postgres crash SOS

From: Dann Corbit <DCorbit(at)connx(dot)com>
To: 'Merlin Moncure' <mmoncure(at)gmail(dot)com>, 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 20:22:21
Message-ID: 87F42982BF2B434F831FCEF4C45FC33E0C1E3046@EXCHANGE.corporate.connx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Merlin Moncure
> Sent: Thursday, June 17, 2010 12:56 PM
> To: Tom Lane
> Cc: Felde Norbert; pgsql-general(at)postgresql(dot)org; Scott Marlowe
> Subject: Re: [GENERAL] postgres crash SOS
>
> On Thu, Jun 17, 2010 at 2:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > You weren't too specific about how you got into this state, but I
> > suppose that it must have been a system crash or power failure.  Even
> > then, you would not have gotten burnt if the filesystem and hardware
> > did what they're supposed to do.  I suspect you have a setup wherein
> > fsync() calls aren't being honored properly.  You may need to disable
> > write caching on your disks, and/or switch to another filesystem or
> OS.
> > (Personally I'd never run a database I cared about on Windows.)
>
> Although I don't run pg/windows anymore, I did for years and I think
> you're right -- I bet there was a hard reset event and either fsync
> was off or not being honored properly. I was communicating with the
> OP off list to see if there was any evidence of disk full condition
> (no response yet). I never saw any data corruption in line with this
> w/o some external trigger.
>
> In regards to windows/pg generally, I don't think it's all that bad.
> The windows NT kernel is absolutely rock solid stable (quite frankly,
> moreso than linux IMO) and very well supported in terms of hardaware.
> otoh, windows kernel configuration is wacky, the shell sucks, insanely
> overdesigned security model, posix not really supported, etc. It's a
> mixed bag for sure.

I think that the bottom line is that {like any DBMS system} effort is needed to make PostgreSQL run smoothly on any platform, but for Windows support is still fairly new, while on POSIX systems all the kinks have had plenty of time to get worked out. So it should not be unexpected that there will be more problems seen on Windows platforms than on POSIX type platforms. Even so, I think that the progress on Windows has been excellent and that PostgreSQL is definitely a viable alternative to traditional commercial systems. In all cases (Windows or other alternatives) we should use thoroughly tested and carefully configured systems to store our business data.

Nothing new or remarkable here. Just common sense.
IMO-YMMV

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Felde Norbert 2010-06-17 20:51:33 Re: postgres crash SOS
Previous Message Merlin Moncure 2010-06-17 19:56:18 Re: postgres crash SOS