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@xxxxxxxxxx EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
