Date: Wed, 16 Jul 2014 14:45:14 -0500 (CDT)
From: Scott Whitney <scott@journyx.com>
Reply-To: Scott Whitney <swhitney@journyx.com>
To: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin@postgresql.org
Message-ID: 
 <1756032979.492840.1405539914689.JavaMail.zimbra@mail.int.journyx.com>
In-Reply-To: <53C6D524.90305@gmail.com>
References: <53C6D524.90305@gmail.com>
Subject: Re: setting -i and -N 100 when starting postmaster
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_Part_492839_601916107.1405539914688"
Thread-Topic: setting -i and -N 100 when starting postmaster
Thread-Index: T286A3dkca4E+I15vUo3BYvhpqp3Sg==
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

------=_Part_492839_601916107.1405539914688
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

-i is "interactive," as in "listen on TCP/IP" 
-N 384 is max connections 384 

----- Original Message -----

> 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

------=_Part_492839_601916107.1405539914688
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"font-family: times new roman, new york, times, se=
rif; font-size: 12pt; color: #000000"><div>-i is "interactive," as in "list=
en on TCP/IP"</div><div>-N 384 is max connections 384</div><div><br></div><=
div><br></div><hr id=3D"zwchr"><blockquote style=3D"border-left:2px solid #=
1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-=
style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;fo=
nt-size:12pt;">Hi all,<br><div><br></div>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 <br>=
to the same database/same filesystem/same time. Now, they'd like me to fix =
it. Sigh...<br><div><br></div>BTW, this is a V9.2.2 system, and the databas=
e 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 <br>postmaster"=
, I see "service postgresql-9.2 start" uses:<br><div><br></div>postmaster -=
D /opt/datacenter -i -N 384 -p 5431<br><div><br></div>Now, I know what the =
-D and -p are doing, but I'm not sure what -i and -N are for, and my intern=
et search hasn't turned up much. Anybody know?<br>--<br>Jay<br><div><br></d=
iv>PS. Any suggestions beyond setting zero_damaged_pages=3Dtrue and then ru=
nning a vacuum would also be appreciated.<br><div><br></div><br>-- <br>Sent=
 via pgsql-admin mailing list (pgsql-admin@postgresql.org)<br>To make chang=
es to your subscription:<br>http://www.postgresql.org/mailpref/pgsql-admin<=
br></blockquote><div><br></div></div></body></html>
------=_Part_492839_601916107.1405539914688--