On 09/12/16 14:14, Brad DeJong wrote:
Sergey Kim wrote:
> Brad DeJong wrote:
>> Sergey Kim wrote:
>>> ... (loglevel) parameter doesn't produce any messages ...
>> Please verify that your application calls java.sql.DriverManager.setLogWriter(PrintWriter) to set the log destination.
> The following fix gives solution: java.sql.DriverManager.setLogWriter(new java.io.PrintWriter(System.out));
> What should be do in order to preserve the code untouched and still have to JDBC logging available?
Sorry, that is a more difficult question. I am not aware of any way to set the log writer with a configuration parameter rather than by calling setLogWriter().
As for the change in pgjdbc behavior, I suggest creating an issue on https://github.com/pgjdbc/pgjdbc.
This has been raised before. See [1].
The advice to call setLogWriter() along with setLogLevel(...) is necessary if using the api is an option.
That does not work for url property configuring. I have a commit that adds the ability to load a logLevel property on the URL here [2]. Based on 1212.
Jeremy
[1]
https://github.com/pgjdbc/pgjdbc/issues/452 [2]
https://github.com/whitingjr/pgjdbc/tree/logLevel2