Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 833AA2E0052 for ; Tue, 10 Jun 2008 17:00:29 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51571-08 for ; Tue, 10 Jun 2008 17:00:17 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.228]) by developer.postgresql.org (Postfix) with ESMTP id 340222E0037 for ; Tue, 10 Jun 2008 17:00:15 -0300 (ADT) Received: by qb-out-0506.google.com with SMTP id f30so1009872qba.7 for ; Tue, 10 Jun 2008 13:00:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=V7rqulN/71DftOf1qFOwPj4gc9uNQEZ/vF7d0A4Q+xo=; b=hsGSKDgRkgQtaYFs0Vu8ai7PTZJNowh2z3032s1nLmn1L9HHbF4T+Lwx8hbPLJ+KOq Q5MGmEtXlrQI0QaixtW4BUYGmpsIomNnaTGMNNA5fWnggrb48ea/KsCWjn8/d9vzNMby r72N0/4GcmCTB+bBoc+co8m3njSSOcz5vJBy8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=FcxRP0X2i8oO0iZgN5dKyLzqkUKsGa0CARRE7ZcQ405gYY0EQp7xBCh3cz8lzqZili CLxCnjnFjFUyvKwKJUWHxlTzULL+9qVzDBuD/O8ptm3j1pHiBK3+S338Ec6zBC59NP82 UU9kDV5+fD2irtfHr3YzLi+6Cz087CZVxJSXw= Received: by 10.114.134.20 with SMTP id h20mr5552929wad.91.1213128013147; Tue, 10 Jun 2008 13:00:13 -0700 (PDT) Received: by 10.114.130.17 with HTTP; Tue, 10 Jun 2008 13:00:13 -0700 (PDT) Message-ID: Date: Tue, 10 Jun 2008 14:00:13 -0600 From: "Scott Marlowe" To: "Medi Montaseri" Subject: Re: what happend to my database Cc: "Tom Lane" , "Steve Holdoway" , pgsql-admin@postgresql.org In-Reply-To: <8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8078a1730805281837y1ed331bey4e7db16a63423cfa@mail.gmail.com> <20080529135235.d6fcad87.steve.holdoway@firetrust.com> <13918.1212029485@sss.pgh.pa.us> <8078a1730805282214l32d4833j50ccb6c5bb177c9a@mail.gmail.com> <8078a1730806101257m38fd1232nce7ae71870ee5de2@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/82 X-Sequence-Number: 29420 On Tue, Jun 10, 2008 at 1:57 PM, Medi Montaseri wrote: > > > On Tue, Jun 10, 2008 at 12:49 PM, Scott Marlowe > wrote: >> >> On Wed, May 28, 2008 at 11:14 PM, Medi Montaseri >> 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 Me too. Sorry I really shoulda tossed a smily on the end there... :) There's one now...