Hi there.

> > As I said, I need **excellent** performance. I definitely need batch
> > operations, the ability to prepare the statements given as arguments
> > on the configuration file, and not to commit entries one by one, but
> > after a number of entries are ready or (better) after some not so
> > small time. According to the advise I got from experts around here,
> > I'll have to use Oracle Call Interface for this module, I don't know
> > if there are any licensing issues.
>
> I can't comment on the licensing issue, I simply don't know what
> Oracle demands.

I'm not sure how GPL-compatible it is to link to already existing
proprietary code. Anyways, first I code, then we test, then we (you,
actually) decide the legal aspects.

> On thing to do it is let the output module handle the "combination
> work" together. The output module is called one per message, however,
> it does not mean the output must directly write them to the
> database. It may buffer them until the batch is large enough. But this
> currently needs to be implemented on the output module basis.
> Obviously, that will not make coding simpler.

That's what I expected, indeed.


> > It seems I'll have to review how rsyslog's queing modules work...
>
> I would suggest not to move into them - but, of course, if you like
> to... Lol, this is the non-trival task I talked about, there are
> numerous subtleties and, of course, they are weakly documented (but
> the inline doc is quite good).

OK. I'll just have a buffer of entries to be committed.

> Do you have a time frame for your project? (and maybe a rough overview
> of the "big picture" - I am always soooo curios ;))

Not a full timescale. Let's say that as soon as you can provide me with
the documentation/skeleton module most (say 70%) of my work will be
developing this output module. Then, when I understand what a bad
nightmare OCI is I'll be able to give a full timescale. After looking at
ompgsql, it looks like writing output modules is easy if you know what
you're doing. ;)

Then, I'll be able to provide support for this module (fixing bugs and
so on) for a couple of years, so it won't be shoot and forget.

Cheers.
-- 
Luis Fernando Muñoz Mejías
[email protected]

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to