From: Damien M. <dm_mailings@abelia-decors.com>
To: pgsql-php@postgresql.org
Subject: Re: resources limit php -> postgre
Date: 22 Apr 2003 11:18:41 -0000
Message-ID: <20030422111841.17379.qmail@abelia-decors.com> (raw)
Seems it's not after all a Postgre problem... The Apache/php server was in
fact very slow due to loops, but not totally unavailable... A bigger CPU
helped a lot.
And indeed, lowering max_execution_time helps a lot !
Thanks for your replies !
> > You can set a maximum time for execution. This is set for every
> script in
> > php.ini with max_execution_time (default is 30 seconds).
>
> Thanks for your answer. but this has already been done.
> And until it aborts (30 sec) no more DB access...
>
> What I'm looking for is a setting or a way to NEVER let 1 php script
> hangs the entire database resources ?
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: dm_mailings@abelia-decors.com
Subject: Re: resources limit php -> postgre
In-Reply-To: <20030422111841.17379.qmail@abelia-decors.com>
References: <20030422111841.17379.qmail@abelia-decors.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox