The changelog of rsyslog-7.6.0 contains the following entry: ompgsql bugfix: improper handling of auto-backgrounding mode. If rsyslog was set to auto-background itself (default code behaviour, but many distros now turn it off for good reason), ompgsql could not properly connect. This could even lead to a segfault. The core reason was that a PG session handle was kept open over a fork, something that is explicitely forbidden in the PG API. Thanks to Alain for the analysis and the patch.
This is consistent with what I observed when attempting to track down the issue (ompgsql + auto-backgrounding), see the forwarded: link for more details. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
