| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: In which session context is a trigger run? |
| Date: | 2018-12-31 12:18:45 |
| Message-ID: | CAKLmikMJawYozUxqU0T5pNJay20kmg6AKuYEkurWpnnubtnABQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
On Sun, Dec 30, 2018 at 9:58 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> Doesn’t seem likely. Maybe you can use NOTIFY/LISTEN in your temporary triggers and have your active client perform the work after being notified.
Yes, this is what I ended up doing. I signal the client and then the
client dispatches the call inside the correct client
connection/session. It seems to work fine. Probably latency it is
adding is also not too big a problem for me. I will see through time.
Mitar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitar | 2018-12-31 12:22:20 | Re: In which session context is a trigger run? |
| Previous Message | Peter J. Holzer | 2018-12-31 10:58:38 | Re: In which session context is a trigger run? |