| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| 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:11:10 |
| Message-ID: | 41C4F14E.9050108@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway wrote:
>>
>>
>> So one thing I'd strongly suggest is stopping Postgres and dismounting
>> the NFS server to see what's under there. If there is a valid-looking
>> PGDATA directory under there, you definitely want to get rid of it to
>> reduce the risk of this happening again.
>>
>
> Perhaps we should purposefully place a root owned placeholder file
> there -- that way Postgres would refuse to start at all in this scenario.
>
> BTW, the init script is indeed the one which automatically does initdb:
>
>
ISTM that this should ideally be a sysconfig setting that is picked up
by the init script.
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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-12-19 03:19:30 | Re: buildfarm improvements |
| Previous Message | Joe Conway | 2004-12-19 02:51:56 | Re: production server down |