From: | Jeremy Whiting <jwhiting(at)redhat(dot)com> |
---|---|
To: | Brad DeJong <Brad(dot)Dejong(at)infor(dot)com>, Sergey Kim <skim(at)odin(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org>, Sergey Onuchin <sonuchin(at)odin(dot)com> |
Subject: | Re: Re: logging bug in JDBC driver (https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar) |
Date: | 2016-12-15 16:03:20 |
Message-ID: | 027a7987-01da-9f00-6e42-bf455fcc14c9@redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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
From | Date | Subject | |
---|---|---|---|
Next Message | danap | 2016-12-15 17:29:52 | Re: Re: logging bug in JDBC driver (https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar) |
Previous Message | Dave Cramer | 2016-12-14 19:13:38 | Re: getTypeInfo |