| From: | Adam Tauno Williams <awilliam(at)whitemice(dot)org> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Asynchronous Trigger? |
| Date: | 2018-04-27 19:57:43 |
| Message-ID: | 1524859063.3334.3.camel@whitemice.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 2018-04-27 at 11:25 -0600, Michael Loftis wrote:
> As suggested, note in ToDo table, also maybe look at LISTEN and
> NOTIFY and have a job runner process LISTENing
We use a simple python process to listen with a PostgreSQL cursor for
NOTIFY events, and push them into RabbitMQ (message broker). From
there you can do a lot of asynchronous work; it will store messages,
optionally with expiration, you have point-to-point or broadcast,
etc... It is a very durable, scalable, and flexible way to built up an
event driven system.
--
Meetings Coordinator, Michigan Association of Railroad Passengers
537 Shirley St NE Grand Rapids, MI 49503-1754 Phone: 616.581.8010
E-mail: awilliam(at)whitemice(dot)org GPG#D95ED383 Web: http://www.marp.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2018-04-27 20:36:30 | Re: Rationale for aversion to the central database? |
| Previous Message | Steven Lembark | 2018-04-27 19:50:41 | Re: Long running INSERT+SELECT query |