Re: what happend to my database

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Medi Montaseri" <montaseri(at)gmail(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Steve Holdoway" <steve(dot)holdoway(at)firetrust(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: what happend to my database
Date: 2008-06-10 19:49:16
Message-ID: dcc563d10806101249n22b349a0pfe64c45b15a3320b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, May 28, 2008 at 11:14 PM, Medi Montaseri <montaseri(at)gmail(dot)com> wrote:
> Yes, this type of presumptuous behavior to wipe out a production database
> based on a few checks is too risky...
>
> Behavior one:
> First out-of-box time, pg_ctl does not find any database files, it tells the
> user that "sorry I did not find any database to start....see initdb....
> Result: we have a semi-unhappy user/admin that says... what is initdb
>
> Behavior two:
> In order to enhance the out-of-box experience, we have wiped out a
> production environment, leading to many unhappy staff and customers....
>
> PG developers...I am not impressed at all...

In defense of the pg developers, the behaviour you describe was
removed long ago BECAUSE of the issues you mention.

The fact is that pg developers can't police every distro out there to
make sure they've removed such hinky behaviour from their startup
scripts. So, the persons to NOT be impressed with at all are the
folks who maintain your OS's postgresql packaging, not the pg
developers.

Course, you can always switch to MySQL, or Oracle, or MSSQL where
nothing like that ever happens. uh huh.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Medi Montaseri 2008-06-10 19:57:32 Re: what happend to my database
Previous Message Scott Marlowe 2008-06-10 19:09:52 Re: error handling unique key constraint in pgsql