Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1X7V46-0002GU-56 for pgsql-admin@arkaria.postgresql.org; Wed, 16 Jul 2014 19:40:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1X7V45-0005t0-Lh for pgsql-admin@arkaria.postgresql.org; Wed, 16 Jul 2014 19:40:33 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1X7V44-0005su-Sj for pgsql-admin@postgresql.org; Wed, 16 Jul 2014 19:40:33 +0000 Received: from mail-yk0-x229.google.com ([2607:f8b0:4002:c07::229]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1X7V42-0001kn-0p for pgsql-admin@postgresql.org; Wed, 16 Jul 2014 19:40:31 +0000 Received: by mail-yk0-f169.google.com with SMTP id 131so708271ykp.28 for ; Wed, 16 Jul 2014 12:40:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=A3OR2OlZQXHxBLXQJNfz0qh4c+19bz3Kq0YasnturJo=; b=0MEItK64RReDgAz6PybqPgBBRLZSuh0p6NrgVEMYdb1ZCHr7b3/JLLBDRgF6t5oFPd MQlQCe1wObTm0/Gdgdrj1bSB5Xr+R1mNj5EEfyLArXrqxMMY2P1Qluc6Xp2rHFjCJ8W3 C7+ig86a+s4V7RQSnH1LDZfTP/6E++eFI6KD0F1AQvvf2rQXVgVhvL6fheAeWj/bq94U FDpQhu0CBxsn56QlWhVPYl/MXHAWS4IDdpqjJxJHC2tlGkhp6KJmIVYp0rv7NrkNPH2y SIQxCBJSI57aMqFSvdrbB4pkbFNel+U6B8wWCT4wZdP1D0ktXYW0pHRdQY/Hcav5kpln rkiw== X-Received: by 10.236.110.234 with SMTP id u70mr7235048yhg.160.1405539629027; Wed, 16 Jul 2014 12:40:29 -0700 (PDT) Received: from [192.168.254.2] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id m29sm548296yhb.31.2014.07.16.12.40.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Jul 2014 12:40:28 -0700 (PDT) Message-ID: <53C6D524.90305@gmail.com> Date: Wed, 16 Jul 2014 15:40:20 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: setting -i and -N 100 when starting postmaster Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) 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 Hi all, 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... BTW, this is a V9.2.2 system, and the database will still start, but the logs are full of reports pf invalid page header errors. One thing I'm looking at is doing a "ps -ef | grep postmaster", I see "service postgresql-9.2 start" uses: postmaster -D /opt/datacenter -i -N 384 -p 5431 Now, I know what the -D and -p are doing, but I'm not sure what -i and -N are for, and my internet search hasn't turned up much. Anybody know? -- Jay PS. Any suggestions beyond setting zero_damaged_pages=true and then running a vacuum would also be appreciated. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin