Triggers and System Tables.

Lists: pgsql-sql
From: stef(at)chronozon(dot)artofdns(dot)com (Stef Telford)
To: pgsql-sql(at)postgresql(dot)org
Subject: Triggers and System Tables.
Date: 2002-05-27 22:46:50
Message-ID: 20020527224650.0A27E8AEA@chronozon.artofdns.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-sql


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


From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Stef Telford <stef(at)chronozon(dot)artofdns(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Triggers and System Tables.
Date: 2002-05-28 05:29:05
Message-ID: 20020527222735.V17559-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-sql

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.