| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Graeme Hinchliffe <graeme(dot)hinchliffe(at)zeninternet(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: detecting a dead db not seeming to work |
| Date: | 2004-08-26 15:27:48 |
| Message-ID: | 17959.1093534068@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Graeme Hinchliffe <graeme(dot)hinchliffe(at)zeninternet(dot)co(dot)uk> writes:
> On Thu, 2004-08-26 at 15:57, Tom Lane wrote:
>> A new postmaster can't start until the last old backend is gone. This
>> is a necessary interlock to avoid data corruption.
> But I kill -9 the postmaster, and I cannot start a fresh one, so my
> process is sat in limbo, thinking it is talking to a db that isn't there
> :).
> Well I think so, although I suspect that some part of the db is still
> there and running?
Certainly --- the backend that's serving your connection. See
http://www.postgresql.org/docs/7.4/static/connect-estab.html
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leonardo Francalanci | 2004-08-26 15:43:12 | R: R: space taken by a row & compressed data |
| Previous Message | Tino Wildenhain | 2004-08-26 15:13:42 | Re: space taken by a row & compressed data |