X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2655053AB5 for ; Fri, 13 May 2005 13:15:16 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69525-01 for ; Fri, 13 May 2005 16:15:11 +0000 (GMT) Received: from singleton-labs.lt (unknown [193.219.160.108]) by svr1.postgresql.org (Postfix) with ESMTP id EA61D539FC for ; Fri, 13 May 2005 13:15:09 -0300 (ADT) Received: from [10.1.10.101] (helo=[10.1.10.101]) by singleton-labs.lt with asmtp (Exim 4.34) id 1DWd5g-0003w7-9l for pgsql-admin@postgresql.org; Fri, 13 May 2005 19:32:44 +0300 Message-ID: <4284D2B1.7040609@singleton-labs.lt> Date: Fri, 13 May 2005 19:15:45 +0300 From: Saulius Malakauskas User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Problem with pltcl trigger Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200505/226 X-Sequence-Number: 17655 We have problem with pltcl triggers. We have table with unique field on which executes a emty pltcl trigger after update, insert and delete. Situation is: 1. Starting new seassion; 2. Executing first update query without exceptions; 3. Executing second update query with unique exception; 4. Closing seassion. Sometimes, when this seasion repeated many times without waiting, seasion closes abnormaly postmaster process is defunct. DEBUG log for defunct seasion has only this difference from normal seassion: -------------------------------------------------------------------------------------------- DEBUG: reaping dead processes DEBUG: child process (PID 20805) exited with exit code 0 --------------------------------------------------------------------------------------------- And the are no more exceptions or smth. When trigger is dropped or function is plpgsql seassions closes normaly. Pltcl triggers would be used later for column changes logging, but this abnormal situation stops our works. We try change trigger cal before or after but situation was same. Our system parameters are: * debian - kernel 2.4.27-8 * pgsql 7.4.7-7 * tcl 8.4.9-1 * libpgtcl 7.4.7-2 Can you help us in this situation, or give some advice? Saulius M.