| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Scalia <jayknowsunix(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: setting -i and -N 100 when starting postmaster |
| Date: | 2014-07-16 22:05:26 |
| Message-ID: | 5100.1405548326@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
John Scalia <jayknowsunix(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Ramanauskas | 2014-07-17 08:58:31 | Re: Cloning PostgreSQL 8.3.7 |
| Previous Message | Jerry Sievers | 2014-07-16 21:07:02 | Re: Cloning PostgreSQL 8.3.7 |