From: | Jonathan Pool <pool(at)utilika(dot)org> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Postmaster stops after starting--solution |
Date: | 2005-01-20 02:43:04 |
Message-ID: | 02626E4A-6A8D-11D9-95C8-0003935AF7F6@utilika.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
In the October 2004 thread "postmaster stopps" Tom Lane et al.
suggested better logging to capture error messages when postmaster
silently stops after starting. I was getting silent stops whenever
booting the host, so I tried to follow that advice. I found that
redirecting the standard and error output to a named file instead of
/dev/null didn't merely capture the error messages, but stopped the
error from occurring in the first place. So, I appreciate that advice
greatly.
This is under the current version of Red Hat Enterprise Linux AS
running PostgreSQL 7.4.5, starting it at boot time with a custom
version of Ryan Kirkpatrick's /etc/rc.d/init.d/pgsql file.
From | Date | Subject | |
---|---|---|---|
Next Message | Theo Galanakis | 2005-01-20 03:08:52 | Command prompt replication. |
Previous Message | Michael Fuhr | 2005-01-19 18:20:01 | Re: Building a list of fields ? |