| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | lapham(at)jandr(dot)org |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: restarting after power outage |
| Date: | 2005-04-27 18:26:22 |
| Message-ID: | 24884.1114626382@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jon Lapham <lapham(at)jandr(dot)org> writes:
> After a power outage (and bad UPS combo, or plug pull, or bad RAM, etc)
> sometimes (I would guess <10% of the time) postgresql fails to restart
> automatically after booting the computer. Invariably, it is because the
> "postmaster.pid" file exists, but maybe this is just a symptom of
> something else. The solution I have been performing is to simply delete
> this file, and then restart postgres (service postgresql start).
> Is this the correct procedure?
It is. We have been fooling with the postmaster startup logic to try to
eliminate this gotcha, but it's only very recently (8.0.2) that I think
we got it right.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Liu | 2005-04-27 18:32:27 | dump and restore a single table containing large objects |
| Previous Message | Michael Fuhr | 2005-04-27 18:16:16 | Re: populating a table via the COPY command using C code. |