| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Enhancement proposal - detect chain of triggers from inside the trigger |
| Date: | 2013-01-16 08:53:58 |
| Message-ID: | CAFj8pRBa2_X0o0abLBprchEqHD-Eb_vSemLPNCBH7W-EyHqUxw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2013/1/16 Edson Richter <edsonrichter(at)hotmail(dot)com>:
> I was wondering, would be a nice addition the ability to read the chain of
> triggers (may be another trigger variable like TG_OP, called "TG_CHAIN" or
> something else that will be an array with the name of the triggers called
> before current trigger).
-1
building dynamic used array, that should or should not used can
significantly decrease performance :(
if you need it, you can use workaround - session variables.
Regards
Pavel Stehule
>
> Would help debug database triggers that have cascaded events.
>
> Regards,
>
> Edson
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
| From | Date | Subject | |
|---|---|---|---|
| Next Message | SUNDAY A. OLUTAYO | 2013-01-16 10:26:45 | Re: Linux Distribution Preferences? |
| Previous Message | Tatsuo Ishii | 2013-01-16 06:54:13 | Re: [pgpool-general: 1315] Re: Database connections seemingly hanging |