Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X7XKW-0008HC-FP for pgsql-admin@arkaria.postgresql.org; Wed, 16 Jul 2014 22:05:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X7XKV-00070R-Mq for pgsql-admin@arkaria.postgresql.org; Wed, 16 Jul 2014 22:05:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X7XKT-00070I-O1 for pgsql-admin@postgresql.org; Wed, 16 Jul 2014 22:05:37 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X7XKL-0007RE-Lu for pgsql-admin@postgresql.org; Wed, 16 Jul 2014 22:05:36 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s6GM5QXo005101; Wed, 16 Jul 2014 18:05:26 -0400 From: Tom Lane To: John Scalia cc: "pgsql-admin@postgresql.org" Subject: Re: setting -i and -N 100 when starting postmaster In-reply-to: <53C6D524.90305@gmail.com> References: <53C6D524.90305@gmail.com> Comments: In-reply-to John Scalia message dated "Wed, 16 Jul 2014 15:40:20 -0400" Date: Wed, 16 Jul 2014 18:05:26 -0400 Message-ID: <5100.1405548326@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org John Scalia writes: > My wonderful colleagues in charge of our production database have screwed up royally. They managed to corrupt the production database by having two instances of postgresql talking > to the same database/same filesystem/same time. Now, they'd like me to fix it. Sigh... Just outta curiosity, how'd they do that? There are interlocks that are supposed to prevent it. You can defeat the interlocks by manually deleting the postmaster lock file, which is why you're *never* supposed to do that. I'm curious if they did that, or found some new way. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin