Re: Possible causes for database corruption and solutions

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: Michael Clark <codingninja(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Possible causes for database corruption and solutions
Date: 2009-12-16 04:48:25
Message-ID: dcc563d10912152048y2b130c96h801b5fd65860a96@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Dec 15, 2009 at 7:45 PM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Florian Weimer 2009-12-16 07:54:39 Re: Possible causes for database corruption and solutions
Previous Message Ron Mayer 2009-12-16 04:23:17 Re: Possible causes for database corruption and solutions