pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Medi Montaseri <montaseri@gmail.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Steve Holdoway <steve.holdoway@firetrust.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: what happend to my database
Date: Tue, 10 Jun 2008 12:57:32 -0700
Message-ID: <8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com> (raw)
In-Reply-To: <dcc563d10806101249n22b349a0pfe64c45b15a3320b@mail.gmail.com>
References: <8078a1730805281837y1ed331bey4e7db16a63423cfa@mail.gmail.com>
	<20080529135235.d6fcad87.steve.holdoway@firetrust.com>
	<13918.1212029485@sss.pgh.pa.us>
	<8078a1730805282214l32d4833j50ccb6c5bb177c9a@mail.gmail.com>
	<dcc563d10806101249n22b349a0pfe64c45b15a3320b@mail.gmail.com>

On Tue, Jun 10, 2008 at 12:49 PM, Scott Marlowe <scott.marlowe@gmail.com>
wrote:

> On Wed, May 28, 2008 at 11:14 PM, Medi Montaseri <montaseri@gmail.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.


stand corrected


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


Never...I rather stay and fix it...than run away to a different country

Thanks

view thread (7+ messages)  latest in thread

Message-ID: <8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com>
Permalink:  ../8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com/
Also on:    postgresql.org/message-id/8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: montaseri@gmail.com, scott.marlowe@gmail.com, tgl@sss.pgh.pa.us, steve.holdoway@firetrust.com
  Subject: Re: what happend to my database
  In-Reply-To: <8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox