| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Mason Hale <mason(at)onespot(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: unable to fail over to warm standby server |
| Date: | 2010-01-29 06:54:28 |
| Message-ID: | 3f0b79eb1001282254ga31fdddob67ed78853759a12@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Jan 29, 2010 at 12:03 AM, Mason Hale <mason(at)onespot(dot)com> wrote:
> Of course the best solution is to avoid this issue entirely. Something as
> easy to miss as file permissions should not cause data corruption,
> especially in the process meant to fail over from a crashing primary
> database.
I believe that such a file permission problem does nothing but
shut down the standby by a FATAL error, and wouldn't cause data
corruption. So if you remove the trigger file with a wrong
permission after the shutdown, you can restart a recovery well
by just starting the standby postgres.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodger Donaldson | 2010-01-29 08:07:21 | Re: Amazon EC2 CPU Utilization |
| Previous Message | Craig Ringer | 2010-01-29 00:51:45 | Re: emedded SQL in C to get the record type from plpgsql |