Other than shutting down unexpectedly the server works fine.
I now have the server running as a remote host on my computer. I have been
running it on localhost.
It was shutting down when I was attempting to connect with my application. I
didn't think too much about it figuring I would find the problem in my app.
However when PG Admin force the server to close I began to think it was
something else.
I simply clicked 'connect' in PG Admin and got the error.
There are 6 databases and I make a single connection to one of them (still
in development stage).
I can't be sure wheter PG Admin forced a shutdown when I was on localhost
although my application attempting to conect did force a shutdown.
A simple 'stop' then 'start' resolves the immediate problem.
Bob
----- Original Message -----
From: "Steve Crawford" <scrawford@xxxxxxxxxxxxxxxxxxxx>
To: "Bob Pawley" <rjpawley@xxxxxxx>
Cc: "PostgreSQL" <pgsql-general@xxxxxxxxxxxxxx>
Sent: Wednesday, March 11, 2009 8:43 AM
Subject: Re: Server Shutting Down
Bob Pawley wrote:
Hi
I've had the server shut itself down when attempting to connect, even
with PG Admin.
Is there anything I can do to ensure that the pg server continues to run
during a connection?
Bob
We're going to need a bit more to go on.
Is it the whole server or just your backend? Did it used to work? What
changed? If you revert changes does it work again? Is the server otherwise
healthy? Are you exceeding something (number of connections, open file
limits or anything else you can think of) so that PG or the OS is killing
the backend? Is the server on the same machine that you are connecting
from? What OS? What do the PostgreSQL server logs say (increase logging
verbosity if necessary)?
Cheers,
Steve
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
