On Fri, Aug 20, 2004 at 06:44:27 -0700,
"Pradeepkumar, Pyatalo (IE10)" <Pradeepkumar.Pyatalo@honeywell.com> wrote:
>
>
> I am sorry for the confusion. One machine, I am running Red Hat Linux - 8.0
> with kernel version 2.4.18.
> Other machines have Red Hat Linux - 7.2 with kernel version 2.4.7
> Hope this is what you are expecting.
Yes.
> I am a newbie to postgresql and Linux, i have no idea about
> .bashrc,.cshrc,.profile.
You are going to want to read documentation on whatever shell you are
using, so as to learn how to configure things to help you work more
efficiently.
If you installed postgres by bulding from a source tar ball, most likely
stuff you want to use without typing the full path got put in /usr/local/bin.
If you install from an rpm, the binaries will normally get put in /usr/bin,
which should be in your path.
> I dont know where the logfile is, i havent checked it. Only thing is in the
> link they have given steps to run postmaster automatically on boot. After
> doing that, it doesnt automatically start after restart....we have to start
> it manually. There is no problem in starting it manually.
This sounds like you may not have told init that postgres is supposed to
be started in your default run level. You probably want to read
'man chkconfig' and then use chkconfig to set things so that postgres
is started by default. I think you will want to run something like:
chkconfig --levels 2345 postgresql on
You will need to do that as root.
>
> In between i noticed some strange thing....
> when I run my application....it is creating a number of postmaster services,
> it was not happening before.
> when say
> $ps -el
> there are more than 10 postmaster services running
>
> Then i get the error message -
> FATAL : sorry too many client connections and other error
> LOG : unexpected EOF on client connection
>
> any inputs on that.
A separate copy of the postmaster gets started for each database connection.
So if your webserver is connecting to your database, having multiple
postmaster processes is expected.
You probably want to set postgres' limit on the number of connections to
be slightly higher than the number of allowed connections to your web
server. A limit of only 10 postmaster processes is likely less than what
your web server is limited to and may be the source of your problem.
