I will try a patch tomorrow:
340 CHKiRet(cflineParseTemplateName(&p, *ppOMSR, 0,
OMSR_RQD_TPL_OPT_SQL, (uchar*) " StdPgSQLFmt"));
341
342 /* If we detect invalid properties, we disable logging,
343 * because right properties are vital at this place.
344 * Retries make no sense.
345 */
346 if (iPgSQLPropErr) {
347 errmsg.LogError(0, RS_RET_INVALID_PARAMS, "Trouble with
PgSQL connection properties. -PgSQL logging disabled");
348 ABORT_FINALIZE(RS_RET_INVALID_PARAMS);
349 } else {
350 CHKiRet(initPgSQL(pData, 0));
# ---> If fork is no we should close the connection.
351 }
And some code to directly call initPgSQL(pData, 0) when the thread is really
used.....
Alain
--
View this message in context:
http://rsyslog-users.1305293.n2.nabble.com/rsyslog-7-4-9-ompgsql-libpq-threads-problem-tp7584204p7584220.html
Sent from the rsyslog-users mailing list archive at Nabble.com.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
