| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Antonios Christofides <anthony(at)itia(dot)ntua(dot)gr>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Cascade delete triggers change user credentials |
| Date: | 2004-02-17 02:48:23 |
| Message-ID: | 6213.1076986103@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> On Mon, 16 Feb 2004, Antonios Christofides wrote:
>> ... this triggers a delete from "b", which in turn activates the
>> show_current_user trigger, the triggered function selects
>> "current_user", and the result is the user who created "b", not the
>> currently connected user.
> The triggered actions occur as if done by the owner of the fktable so that
> they will not fail if the current user does not actually have delete
> access on that table. I'm not sure which result for current_user makes
> more sense in that context for further triggered actions.
I don't think it's a bug. I would suggest that Antonios probably really
wants to be using SESSION_USER, not CURRENT_USER.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Patnude | 2004-02-17 06:03:22 | Re: Repost: Syntax - or unavailability of same - for variable join??? Can anyone help? |
| Previous Message | Tom Lane | 2004-02-17 02:42:32 | Re: Select for update, locks and transaction levels |