| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Jon Lapham <lapham(at)jandr(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Restart after poweroutage |
| Date: | 2006-09-24 16:27:52 |
| Message-ID: | 4516B208.3030500@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> This doesn't make sense to me. A reboot will absolutly kill any
> existing shared memory blocks, how can it possibly be complaining about
> it?
PostgreSQL complains if it finds a postmaster.pid. As far as I can tell
it doesn't have anything to do with shared memory except that we are
tracking info in the postmaster.pid. Info that is no longer valid.
What would make sense to me, would be to read the pid file, check the
process list. If the process that is in the pid file is not in the
process list, we remove the pid file and start.
Sincerely,
Joshua D. Drake
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Chiarappa | 2006-09-24 16:28:35 | Re: Sun Java Studio Creator and PostgreSQL |
| Previous Message | Tom Lane | 2006-09-24 16:17:26 | Re: Restart after poweroutage |