Isaac Morland <isaac.morland@gmail.com> writes:
> I was trying to use triggers, and ran into something I hadn't realized
> until now: triggers run, not as the owner of the table, but as the user who
> is doing the insert/update/delete.
If you don't want that, you can make the trigger function SECURITY
DEFINER. If we forced such behavior, there'd be no way to get the
other behavior.
regards, tom lane