From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Lane Van Ingen <lvaningen(at)esncc(dot)com> |
Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org, stellr(at)cns(dot)vt(dot)edu |
Subject: | Re: What Are Last Steps Performed When PostgreSQL |
Date: | 2006-09-28 16:32:33 |
Message-ID: | 200609281632.k8SGWXb28878@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Lane Van Ingen wrote:
> Forgot about 'pg_ctl status'. That will work fine for my needs.
>
> Ray Stell mentioned it would be helpful to see a description of all the
> things that go on from start to finish, in general or course. I agree. It
> helps to know the logic going on behind the scenes when things break. I had
> a problem in August where PostgreSQL would not come up; I finally traced it
> to broken links in the libraries, but it took a long time to find .... and
> there were no error messages logged to help. Does this kind of information
> exist anywhere?
The information exists only in the source code.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Sriram Dandapani | 2006-09-28 18:16:24 | transaction id wraparound |
Previous Message | Mathias Laurent | 2006-09-28 15:26:36 | SELECT FOR UPDATE NOWAIT |