Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id CF2814761E3 for ; Mon, 27 May 2002 19:29:37 -0400 (EDT) Received: from chronozon.artofdns.com (CPE00e0293a847c.cpe.net.cable.rogers.com [24.100.79.179]) by postgresql.org (Postfix) with ESMTP id DB2614766D2 for ; Mon, 27 May 2002 19:02:15 -0400 (EDT) Received: by chronozon.artofdns.com (Postfix, from userid 501) id 0A27E8AEA; Mon, 27 May 2002 18:46:50 -0400 (EDT) To: pgsql-sql@postgresql.org Subject: Triggers and System Tables. Message-Id: <20020527224650.0A27E8AEA@chronozon.artofdns.com> Date: Mon, 27 May 2002 18:46:50 -0400 (EDT) From: stef@chronozon.artofdns.com (Stef Telford) X-Archive-Number: 200205/286 X-Sequence-Number: 7921 Hello, this is probably a really silly question, but where can i control wether or not the superuser/root user can create a trigger on a system table ? Currently, have been tinkering with the idea of adding in the ability to have 'session variables' for the connection, so that before a transaction it can declare and save variables, so that they can be used in the transaction themselves. This would ease some problems i have with inheritance. It also would make some sort of connection limiting per user a lot easier if it was possible to attach triggers to pg_stat_activity (on INSERT only :) So, the real question is, is this a question for hackers mailing list or can anyone tell me how to drop the limitation ? many thanks Stef