stuff.
Maybe this can be done in a different way than listening for notifications?
From: Pavel Stehule [mailto:pavel.steh...@gmail.com]
Sent: Tuesday, April 26, 2016 11:22 AM
To: Jinhua Luo
Cc: Ihnat Peter | TSS Group a.s.; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Background worker
On 4/27/2016 1:40 AM, Ihnat Peter | TSS Group a.s. wrote:
I don’t want to create client to do some work in the DB if the DB can
do it itself on server side much faster.
The situation is that some data are inserted in to many tables and if
these data need to be post processed a notification
stuff.
Maybe this can be done in a different way than listening for notifications?
From: Pavel Stehule [mailto:pavel.steh...@gmail.com]
Sent: Tuesday, April 26, 2016 11:22 AM
To: Jinhua Luo
Cc: Ihnat Peter | TSS Group a.s.; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Background worker
Why not use libpq in worker? i.e. your worker works just like a pure PG client.
In my project, I uses worker in this way and it works well. I do not
use any backend API to access the database.
2016-04-21 15:51 GMT+08:00 Ihnat Peter | TSS Group a.s. :
> I am trying to create
Hi Peter!
The solution to this problem would be also interesting for me. We have
application which use sending data to background worker and it's look like
the asynchronous notification can be ideal solution. But we do not found
solution how to work with this notifications. Worker calculating
I am trying to create background worker which listens to notifications and do
some work after receiving one.
I got 2 problems:
- Worker is receiving notifications from every channel not only the
registered channel (in my case "foo")
- Notifications are not logged in the