Peter Czanik writes: > And that's right. With MySQL, if I don't configure a port number in > syslog-ng.conf, then the default 3306 is used. Setting the port number > to another value also works fine. > With PostgreSQL if the port is not specified, libdbi tries to connect to > port 0 (zero). It works fine, once a port is specified. > I was told, that in syslog-ng all databases are treated equal, so it's > something in libdbi port handling.
I had to revisit this issue in a different context (libdbi-drivers Bug #3163428). Now pgsql and mysql are supposed to deal with ports the same way. If a string option is used to set the port, this port is used. If no string option is set, but a numeric option is set, use that. If neither is set, the port will be set to zero. This essentially means that applications using libdbi are expected to provide an appropriate port. There is nothing going to happen automagically. If this behaviour is not desired, feel free to request a change. As mentioned previously, we could provide the well-known defaults of pgsql and mysql instead of zero. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ libdbi-devel mailing list libdbi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-devel
