Re: Possible causes for database corruption and solutions - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Possible causes for database corruption and solutions
Date
Msg-id dcc563d10912152048y2b130c96h801b5fd65860a96@mail.gmail.com
Whole thread Raw
In response to Re: Possible causes for database corruption and solutions  (Craig Ringer <craig@postnewspapers.com.au>)
List pgsql-general
On Tue, Dec 15, 2009 at 7:45 PM, Craig Ringer
<craig@postnewspapers.com.au> wrote:
> On 16/12/2009 9:07 AM, Scott Marlowe wrote:
>
>> I'd also recommend moving off of OSX as you're using a minority OS as
>> far as databases are concerned, and you won't have a very large
>> community to help out when things do go wrong.
>
> It sounds like PostgreSQL is being used as a DB bundled with an app - not
> quite embedded, but as close as Pg gets. Right, OP?
>
> If so, they wouldn't be moving off Mac OS X, they'd be moving off Pg.
>
> While Pg doesn't seem to be hugely used on Mac OS X as a production
> environment for running dedicated database servers, it should still work
> safely and with acceptable performance. If it doesn't then good problem
> reports will help improve that. So I for one encourage them to stick with Pg
> and stay in touch on the list. They shouldn't have issues now that they've
> got OS X honouring fsync, and if they do then it'd be good to hear about it.

Oh, I completely missed that they didn't have fsync working right.
Yeah, I agree then, embedded on OSX, fsync working, that's reasonable.

pgsql-general by date:

Previous
From: Ron Mayer
Date:
Subject: Re: Possible causes for database corruption and solutions
Next
From: Florian Weimer
Date:
Subject: Re: Possible causes for database corruption and solutions