Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 32D7247598C for ; Tue, 28 May 2002 01:30:52 -0400 (EDT) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 31F58475955 for ; Tue, 28 May 2002 01:29:08 -0400 (EDT) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 717E1D609; Mon, 27 May 2002 22:29:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 5B17F5C01; Mon, 27 May 2002 22:29:05 -0700 (PDT) Date: Mon, 27 May 2002 22:29:05 -0700 (PDT) From: Stephan Szabo To: Stef Telford Cc: Subject: Re: Triggers and System Tables. In-Reply-To: <20020527224650.0A27E8AEA@chronozon.artofdns.com> Message-ID: <20020527222735.V17559-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200205/288 X-Sequence-Number: 7923 On Mon, 27 May 2002, Stef Telford wrote: > > 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 ? In general this is not something you can safely do. I'm not sure if pg_stat_activity modifications go through something that will fire triggers, but in general you shouldn't expect that they will on system tables.