| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Michael Fuhr <mike(at)fuhr(dot)org>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: production server down |
| Date: | 2004-12-19 03:34:02 |
| Message-ID: | 41C4F6AA.9030002@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> In the absence of that, in your case, certainly the root-owned
> placeholder is a good idea - it seems nicer than disabling on-boot
> startup altogether if you can avoid that.
I'm pretty well convinced at this point that a start on boot init script
is inappropriate when working with NFS attached storage. We really do
need to be sure the mount is OK before starting the database. And we
have the watchdogs in place, and people on call at all times,
specifically to deal with "service down" events.
And while we could always modify the init script to rip out the
"helpful" initdb part, I think the under-the-mount safety file is a
must, unless of course someone thinks of an alternate scenario where it
will do more harm than good ;-).
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-12-19 04:04:43 | Re: Shared row locking |
| Previous Message | Andrew Dunstan | 2004-12-19 03:19:30 | Re: buildfarm improvements |