From: stef@chronozon.artofdns.com
To: sszabo@megazone23.bigpanda.com
To: stef@chronozon.artofdns.com
Cc: pgsql-sql@postgresql.org
Subject: Re: Triggers and System Tables.
Date: Tue, 28 May 2002 01:35:47 -0400 (EDT)
Message-ID: <20020528053547.169468AEA@chronozon.artofdns.com> (raw)
> 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.
It would make sense to assume that, even though the tables
in question are system tables, that triggers can be used
in unison with them. I do, of course, understand the
inherent dangers with attaching triggers (it could
be possible to attach a trigger that would delete user
logins) but then, this is what i want them -for- :)
The limitation would, to my untrained eye, appear to be
completely aberant. The ability to put triggers on
system tables would allow me to (using plpgsql)
* Limit and/or assign a 'number of logins'
* Create and/or use 'connection' or temporary 'global variables'
These may end up being 'quick and dirty' and by no means
tailored to maximum performance, but it would certainly
be a 'start' if nothing else.
regards
Stef
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: stef@chronozon.artofdns.com, sszabo@megazone23.bigpanda.com
Subject: Re: Triggers and System Tables.
In-Reply-To: <20020528053547.169468AEA@chronozon.artofdns.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox