From: Damien M. <dm_mailings@abelia-decors.com>
To: pgsql-php@postgresql.org
Subject: resources limit php -> postgre
Date: 20 Apr 2003 01:57:52 -0000
Message-ID: <20030420015752.13202.qmail@abelia-decors.com> (raw)
Hi,
There is my problem :
When a user runs on my apache-php-pgsql a badly written php script /
page (which for example infinitely loops on an insert or anything else
who saturate my Postgre), other php pages relying on PG become purely
unavailable until this "bad script" aborts.
Is there a way to define a 'per script' limit on php/PG, or anything
else in order to avoid these problems ?
Thank you in advance !
DM
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: <20030420015752.13202.qmail@abelia-decors.com>
References: <20030420015752.13202.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