| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |
| Date: | 2005-07-05 08:56:07 |
| Message-ID: | 42CA4B27.4060407@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian wrote:
>I am not sure what to do with this patch. It is missing dump
>capability, there is no clause to disable all triggers on a table, and
>it uses a table owner check when a super user check is required (because
>of referential integrity).
>
>
From a user's view, a trigger implementing RI isn't a trigger but an
implementation detail he shouldn't need to care about. So for std
triggers, owner check should be sufficient, requiring superuser for RI
triggers only.
This impacts EN/DISABLE TRIGGER ALL too. To touch RI triggers as well,
an additional keyword is needed.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2005-07-05 09:49:39 | Re: [HACKERS] [PATCH] pgcrypto: pgp_encrypt v3 |
| Previous Message | Dave Page | 2005-07-05 07:30:18 | Re: [HACKERS] Dbsize backend integration |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2005-07-05 09:49:39 | Re: [HACKERS] [PATCH] pgcrypto: pgp_encrypt v3 |
| Previous Message | Dave Page | 2005-07-05 07:30:18 | Re: [HACKERS] Dbsize backend integration |