Re: Security implications of untrusted triggers - Mailing list pgsql-general

From Tom Lane
Subject Re: Security implications of untrusted triggers
Date
Msg-id 19340.1137092160@sss.pgh.pa.us
Whole thread Raw
In response to Security implications of untrusted triggers  (Joshua Kramer <josh@bitbuckets.com>)
List pgsql-general
Joshua Kramer <josh@bitbuckets.com> writes:
> I am writing a couple of Perl modules that talk to the outside world: one
> talks to a database (via DBI), and one talks to a Jabber/XMPP server.  I
> want to use these from within a Trigger.

This is most likely a bad idea for reasons that have nothing to do with
security.  Consider what happens when the trigger executes and later in
the transaction there's an error, causing the whole transaction to roll
back.  Now the outside world has changed state and your database has
not.

It's usually better to have an application process that is in charge of
monitoring database state and updating external stuff to match.  See the
archives for many previous discussions of this point.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Plans for 8.2?
Next
From: Angshu Kar
Date:
Subject: MAX without FROM