Garry Dolley wrote:
>
> > Hmm, all the crashes you show us below sound like resource exhaustion
> > issues. That's a nice way to say your feeding silly SQL to the server,
> > and it's _trying_ to do what you ask... How are you driving the server?
> > psql? some sort of CGI? We need more info to help you debug what's
> > happening
> The server is being queried mainly from Perl CGI scripts (just plain
> perl, not mod_perl or FastCGI, etc...)
Which means that each CGI execution will set up and tear down a connection to
the database. This is a LOT of overhead. I would recommend you look into some
serious database connection pooling mechanism like mod_perl+DBI or a webserver
that knows how to do this automatically.
> > Hmm, what do you mean by high load? Do you really have 128 simultanious
> > backends running?
> Well, I would sometimes get the error 'Sorry, too many clients running',
> so I increased the backends to 128.
See above. Each CGI looks to Postgres like a new client connection.
> > These last few sound like you've damaged your DB installation, perhaps
> > from the resource exhaustion problem from earlier.
> The DB seems to be OK though, absolutely no problems AFTER i manage to
> get Postgres up and running again.
>
> Alas, I need a more powerful machine, but in the meantime if there are
> any other tips you guys can give me, I'd greatly appreciate it!
You should read through http://photo.net/wtr/thebook as it discusses the issues
related to serving high-volume db-backed websites.
HTH,
Brian
--
[EMAIL PROTECTED]
http://www.baquiran.com
US Fax: (603) 908-0727
AIM: bbaquiran
