| From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | setting -i and -N 100 when starting postmaster |
| Date: | 2014-07-16 19:40:20 |
| Message-ID: | 53C6D524.90305@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Whitney | 2014-07-16 19:45:14 | Re: setting -i and -N 100 when starting postmaster |
| Previous Message | Tomas Ramanauskas | 2014-07-16 16:34:10 | Cloning PostgreSQL 8.3.7 |