AM- The band-aid patch is to increase the number of connections available. Check out this link to the idocs:
http://www.postgresql.org/idocs/index.php?runtime-config.html Maybe that will keep things running for you while you go over the code to learn why you're using more connections now. If you aren't using pooled connections, maybe you just have more users on the web. -Nick > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:pgsql-admin-owner@;postgresql.org]On Behalf Of A.M. > Sent: Friday, November 08, 2002 12:31 PM > To: [EMAIL PROTECTED] > Subject: [ADMIN] FATAL 1: Sorry, too many clients already > > > OMG, I'm about to rip my hair out. I've been writing a webapp using > DBD::Pg and it has been accessing postgresql for weeks without > problems. Suddenly this morning with no changes to the setup, I get: > FATAL 1: Sorry, too many clients already > whenever I try to use the webapp (running under user "apache"). This > message appears when I have psql open and in the httpd error_log. > However, if I connect using psql via the domain socket or tcp socket, I > have no problems! I restarted postgres, apache, and the entire server > and the shit won't go away. What am I doing wrong?! > Setup: > RedHat 7.1 > pgsql 7.2.2 > Nothing other than the db and webapp are running on the server. What > should I do? > ><><><><><><><><>< > AgentM > [EMAIL PROTECTED] > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html > ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
