PostgreSQL listen/notify and the method stack

Doug Easterbrook doug at
Thu Nov 23 12:37:43 UTC 2023

As far as I understand the timer is popped on the stack

It’s the same as background workers

So it eventually gets executed as the omnis stack winds down

Just make sure your variable scope is right and you won’t have problems

All Timers act the same way 

Doug Easterbrook
Arts Management Systems Ltd.
doug at

> On Nov 23, 2023, at 2:48 AM, Nick Renders via omnisdev-en <omnisdev-en at> wrote:
> Hello fellow Omnis-Potents,
> I have noticed that when implementing the $listen and $notify methods of the PostgreSQL DAM, the $notify method actually interrupts the current method stack. So when Omnis is executing a certain method, the notification will cut in, execute the $notify method, and return to the previous method where it left off. At least that is what I've come to understand after doing some tests.
> I'm not very comfortable with the $notify method interrupting any possible method at any possible time. Has anyone encountered this before? Does anyone have any good tips and/or tricks on managing listeners/notifiers?
> Best regards,
> Nick Renders
> _____________________________________________________________
> Manage your list subscriptions at
> Start a new message -> mailto:omnisdev-en at

More information about the omnisdev-en mailing list