From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: setting -i and -N 100 when starting postmaster
Date: Wed, 16 Jul 2014 18:05:26 -0400
Message-ID: <5100.1405548326@sss.pgh.pa.us> (raw)
In-Reply-To: <53C6D524.90305@gmail.com>
References: <53C6D524.90305@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
John Scalia <jayknowsunix@gmail.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jayknowsunix@gmail.com
Subject: Re: setting -i and -N 100 when starting postmaster
In-Reply-To: <5100.1405548326@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox