On Sat, 12 Sep 1998, Roelof Osinga wrote:
> Stephane Dupille wrote:
> >
> > Hi there !
> >
> > I got a problem with postgres on a heavy-loaded machine.
> >
> > I use postgres for a web-server. I access the database with a perl-5
> > CGI.
>
> A possible solution would b
Stephane Dupille wrote:
>
> Hi there !
>
> I got a problem with postgres on a heavy-loaded machine.
>
> I use postgres for a web-server. I access the database with a perl-5
> CGI.
A possible solution would be to switch to PHP3. You didn't say
what webserver you're using
On Fri, 11 Sep 1998, Chris Johnson wrote:
> Come on now - this isn't a real solution! If the site is popular then he
> will get more than 50 connections... fastcgi or not he will be over that
> limit.
Hm... i think on about three things:
- Opening a connection does have some ov
Come on now - this isn't a real solution! If the site is popular then he
will get more than 50 connections... fastcgi or not he will be over that
limit.
Chris
--
As I learn the innermost secrets of the people around me, they reward
me in many ways to keep me quiet.
On Fri, 11 Sep 1998, Aldrin
> When I try to access the database with 50 simultaneous connections,
>the database crash, when I use the -o-F option for postmaster, and
>doesn't crash if I do not use it.
I suggest you to reduce the load postgresql receives. A trick is to use
FastCGI, turning cgi sessions into full-time d
Hi there !
I got a problem with postgres on a heavy-loaded machine.
I use postgres for a web-server. I access the database with a perl-5
CGI.
When I try to access the database with 50 simultaneous connections,
the database crash, when I use the -o-F option for po
