X-Original-To: pgsql-php@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id ABABB4758E6 for ; Sat, 19 Apr 2003 21:57:21 -0400 (EDT) Received: from abelia-decors.com (AAmiens-106-2-1-70.abo.wanadoo.fr [193.251.183.70]) by postgresql.org (Postfix) with SMTP id B442B4758C9 for ; Sat, 19 Apr 2003 21:57:20 -0400 (EDT) Received: (qmail 13203 invoked by uid 48); 20 Apr 2003 01:57:52 -0000 Date: 20 Apr 2003 01:57:52 -0000 Message-ID: <20030420015752.13202.qmail@abelia-decors.com> From: "Damien M." To: pgsql-php@postgresql.org Subject: resources limit php -> postgre X-Mailer: NeoMail 1.25 X-IPAddress: 193.253.244.180 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Status: No, hits=-5.8 required=5.0 tests=BAYES_10 version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/19 X-Sequence-Number: 1989 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