Pavel Stehule <pavel.stehule@xxxxxxxxx> writes: > 2013/1/16 Edson Richter <edsonrichter@xxxxxxxxxxx>: >> 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 :( I agree it wouldn't do to add cycles to every trigger for a feature that only a small minority of them would use. However, maybe we could expose something like this as a function you'd call to get the information if you want it, with nil-or-close-to-nil overhead if you don't. In the long run, maybe some of the lesser-used existing trigger variables should be converted to that style too ... regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
