Ok, think I got it,
I can use LISTEN and NOTIFY to do my IPC stuf, will just have to see if
it's possible to listen in a worker, with a permanent server connection,
I guess.
(as I remember, I already did a "listener" 10 years ago in a C client
app.)
Thanks,
Jaquest K.
On Wed, 2015-08-19 at 16:5
Bill Moran wrote:
> On Wed, 19 Aug 2015 19:45:47 +0200
> jacques klein wrote:
>
> > Well, sorry David, I don't understand what you mean,
> >
> > let me explain what I want to do: in short, IPC between "background
> > workers".
> >
> > I am trying to transform my app. from a multi-threaded C SQL
On Wed, 19 Aug 2015 19:45:47 +0200
jacques klein wrote:
> Well, sorry David, I don't understand what you mean,
>
> let me explain what I want to do: in short, IPC between "background
> workers".
>
> I am trying to transform my app. from a multi-threaded C SQL-client into
> some "background work
Well, sorry David, I don't understand what you mean,
let me explain what I want to do: in short, IPC between "background
workers".
I am trying to transform my app. from a multi-threaded C SQL-client into
some "background workers", execution speed beeing the goal (avoid
network io).
Worker start/s
On Wed, Aug 19, 2015 at 05:37:31PM +0200, jacques klein wrote:
> I would like to execute a trigger function (written in C) in one of my
> background workers.
>
> Didn't figure out how to do that not even if it's possible.
You can write your trigger function in such a way as not to do the
usual ch
I would like to execute a trigger function (written in C) in one of my
background workers.
Didn't figure out how to do that not even if it's possible.
Currently my trigger function is called, but in the "server-process"
connected to the client who does the "insert into ..." .
Any hint/help is we
