Hi! On Mon, Dec 31, 2018 at 2:58 AM Peter J. Holzer <hjp-pgsql@xxxxxx> wrote: > On 2018-12-30 08:56:13 -0800, Adrian Klaver wrote: > > On 12/30/18 3:08 AM, Peter J. Holzer wrote: > > > If I understood Mitar correctly he wants the trigger to execute in the > > > session where it was declared, not in the sessio where the statement was > > > executed that triggered the trigger. > > > > There is the additional hitch that the trigger is being declared to use a > > temporary function that is defined in an alias schema pg_temp. > > Yeah, but that would be neatly solved by the magic teleportation of the > trigger execution. (I think this is actually how he got the idea that > executing the trigger in a different session would solve his problem.) Thanks for understanding well what I am asking. Yes, it seems some form of sending around triggers would be needed. I do not really care if those triggers would run after transaction is committed. So they should be some REALLY AFTER triggers. :-) For now I am using NOTIFY/LISTEN to send information to the client which then dispatches it to current connection/session. It allows me also to batch multiple trigger calls together. Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m
