| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: psql should show disabled internal triggers |
| Date: | 2013-09-18 15:00:05 |
| Message-ID: | 052B23EEA79F9BA92D7163A4@apophis.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On 18. September 2013 15:19:27 +0200 Andres Freund
<andres(at)2ndquadrant(dot)com> wrote:
> Well, that will lead the user in the wrong direction, won't it? They
> haven't disabled the constraint but the trigger. Especially as we
> already have NOT VALID and might grow DISABLED for constraint
> themselves...
>
Valid point. But it is also nice to know in detail, which constraints
stopped working. Ok, it is documented which constraints are affected and
maybe i'm lost within too much detail atm, but i find people getting
confused about this internal trigger thingie sometimes. Won't they get
confused about a suddenly appearing RI_ConstraintTrigger_a_54015, too?
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-09-18 15:06:50 | Re: record identical operator |
| Previous Message | Peter Eisentraut | 2013-09-18 14:56:36 | Re: [PATCH] Add an ldapoption to disable chasing LDAP referrals |