ok, probably the decision is correct but I see there should be remarks done in the documentation.
We still see messages that is attempts to log messages in null appender. Why not to log into standard common log. For instance the java.util.logging could be used here.
Best Regards,
Sergey.
From: Jeremy Whiting <jwhiting@redhat.com> Sent: Friday, December 16, 2016 4:34:02 PM To: Sergey Kim Cc: Brad DeJong; pgsql-jdbc@postgresql.org; Sergey Onuchin Subject: Re: [JDBC] Re: logging bug in JDBC driver (https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)
Hi Sergey, The bad news is this will not be going into the mainline. I've had the discussion in the past. The community decision at the time was devs should do a local build to set a PrintWriter. I bear no grudges btw on this decision. There are compelling reasons for it.
So no, it won't be in any Maven repo any time soon. It exists on a branch on GitHub. Floating in the digital ether going nowhere. But you are welcome to copy and paste the code to build your own driver artifact.
Regards, Jeremy
On 15/12/16 18:47, Sergey Kim wrote:
Hi Jeremy,
thank you for the good news.
But will it able to receive the compiled version of the driver? Also it seems it should be published in public maven repositories. Right?
>>> ... (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().
