Postgres Pro
Downloads
Home   >   mailing lists

Thread: [JDBC] logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

[JDBC] logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

Dear Community,



we upgraded our old using jdbc driver with the newest version (https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar) and revealed that ( loglevel) parameter doesn't produce any messages as it stated in the documentation (https://jdbc.postgresql.org/documentation/94/connect.html). 


The previously using but obsolete version (postgresql-9.2-1002.jdbc4.jar) has this feature which we actively have been using for debug purposes.

jdbc.postgresql.org
Connecting to the Database. With JDBC, a database is represented by a URL (Uniform Resource Locator). With PostgreSQL™, this takes one of the following forms:


Please consider the issue.



Best Regards,
Sergey Kim
HA Arhitect / skim@odin.com
http://www.odin.com

[JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Brad DeJong
Date:

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.

 

I just tested loglevel in PostgreSQL JDBC Driver 42.0.0.SNAPSHOT and including loglevel=2 in the JDBC connection string sets the loglevel correctly but the driver will only log messages if there is a valid LogWriter.

Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Brad DeJong
Date:

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.

 

I just tested loglevel in PostgreSQL JDBC Driver 42.0.0.SNAPSHOT and including loglevel=2 in the JDBC connection string sets the loglevel correctly but the driver will only log messages if there is a valid LogWriter.

[JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

Dear Brad DeJong,


in stdlog we see messages:

log4j:ERROR Attempted to append to closed appender named [null].



The following fix gives solution: java.sql.DriverManager.setLogWriter(new java.io.PrintWriter(System.out)); 

But it is related to the code modification routines.  


What should be do in order to preserve the code untouched and still have to JDBC logging available? We just replaced the driver.



Best Regards,
Sergey Kim

From: Brad DeJong <Brad.Dejong@infor.com>
Sent: Friday, December 9, 2016 4:17:44 PM
To: Sergey Kim; pgsql-jdbc@postgresql.org
Cc: Sergey Onuchin
Subject: RE: logging bug in JDBC driver (https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)
 

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.

 

I just tested loglevel in PostgreSQL JDBC Driver 42.0.0.SNAPSHOT and including loglevel=2 in the JDBC connection string sets the loglevel correctly but the driver will only log messages if there is a valid LogWriter.

Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

Dear Brad DeJong,


in stdlog we see messages:

log4j:ERROR Attempted to append to closed appender named [null].



The following fix gives solution: java.sql.DriverManager.setLogWriter(new java.io.PrintWriter(System.out)); 

But it is related to the code modification routines.  


What should be do in order to preserve the code untouched and still have to JDBC logging available? We just replaced the driver.



Best Regards,
Sergey Kim

From: Brad DeJong <Brad.Dejong@infor.com>
Sent: Friday, December 9, 2016 4:17:44 PM
To: Sergey Kim; pgsql-jdbc@postgresql.org
Cc: Sergey Onuchin
Subject: RE: logging bug in JDBC driver (https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)
 

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.

 

I just tested loglevel in PostgreSQL JDBC Driver 42.0.0.SNAPSHOT and including loglevel=2 in the JDBC connection string sets the loglevel correctly but the driver will only log messages if there is a valid LogWriter.

[JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Brad DeJong
Date:

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.

 

Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Brad DeJong
Date:

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.

 

Re: Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Jeremy Whiting
Date:
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

Re: [JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Jeremy Whiting
Date:
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

Re: [JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
danap
Date:
Jeremy Whiting wrote:

>    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

Are any of the other url property configuring settings still working
since changes that broke loglevel, ex. ssh, etc.

Re: Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
danap
Date:
Jeremy Whiting wrote:

>    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

Are any of the other url property configuring settings still working
since changes that broke loglevel, ex. ssh, etc.

Re: Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

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?



Best Regards,
Sergey Kim

From: Jeremy Whiting <jwhiting@redhat.com>
Sent: Thursday, December 15, 2016 7:03:20 PM
To: Brad DeJong; Sergey Kim
Cc: 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)
 
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

Re: [JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

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?



Best Regards,
Sergey Kim

From: Jeremy Whiting <jwhiting@redhat.com>
Sent: Thursday, December 15, 2016 7:03:20 PM
To: Brad DeJong; Sergey Kim
Cc: 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)
 
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

Re: Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Jeremy Whiting
Date:
On 15/12/16 17:29, danap wrote:
> Jeremy Whiting wrote:
>
>>    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
>
> Are any of the other url property configuring settings still working
> since changes that broke loglevel, ex. ssh, etc.
>
>

Back when PR452 was proposed only logging was affected. A refactoring
effort in PR407 stripped out this line

https://github.com/pgjdbc/pgjdbc/pull/407/files#diff-5a70ae121bb9bd3ff288a7f879b0f853L1295

Re: [JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Jeremy Whiting
Date:
On 15/12/16 17:29, danap wrote:
> Jeremy Whiting wrote:
>
>>    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
>
> Are any of the other url property configuring settings still working
> since changes that broke loglevel, ex. ssh, etc.
>
>

Back when PR452 was proposed only logging was affected. A refactoring
effort in PR407 stripped out this line

https://github.com/pgjdbc/pgjdbc/pull/407/files#diff-5a70ae121bb9bd3ff288a7f879b0f853L1295

Re: Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Jeremy Whiting
Date:
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?



Best Regards,
Sergey Kim

From: Jeremy Whiting <jwhiting@redhat.com>
Sent: Thursday, December 15, 2016 7:03:20 PM
To: Brad DeJong; Sergey Kim
Cc: 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)
 
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



Re: [JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Jeremy Whiting
Date:
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?



Best Regards,
Sergey Kim

From: Jeremy Whiting <jwhiting@redhat.com>
Sent: Thursday, December 15, 2016 7:03:20 PM
To: Brad DeJong; Sergey Kim
Cc: 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)
 
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



Re: [JDBC] Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

Hi Jeremy,



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?



Best Regards,
Sergey Kim

From: Jeremy Whiting <jwhiting@redhat.com>
Sent: Thursday, December 15, 2016 7:03:20 PM
To: Brad DeJong; Sergey Kim
Cc: 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)
 
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



Re: Re: logging bug in JDBC driver(https://jdbc.postgresql.org/download/postgresql-9.4.1212.jar)

From
Sergey Kim
Date:

Hi Jeremy,



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?



Best Regards,
Sergey Kim

From: Jeremy Whiting <jwhiting@redhat.com>
Sent: Thursday, December 15, 2016 7:03:20 PM
To: Brad DeJong; Sergey Kim
Cc: 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)
 
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