e
events, and that's kind of a shame IMO.
-rektide
On Tue, Dec 11, 2012 at 12:58:21PM -0800, Sergey Konoplev wrote:
> Hi,
>
> On Tue, Dec 11, 2012 at 11:29 AM, rektide wrote:
> > Does anyone have suggestions for decoupling work done on a server, for
> > breaking up a t
I've described 1. a viable if ugly
means of
doing so, and 2. limitations in the primary asynchronous toolsuite of Postgres,
and am
looking for ways to make more progress.
Regards,
-rektide
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi pgsql-general,
I'm interested in writing a supervisory process that can insure worker
processes are
running/spawn new ones if not. These workers will mainly be responsible for
LISTENing to
the db, which is emitting triggered_change_notification s.
Is there any means to check a NOTIFY queue t
