Hi Adrian,
Thanks a lot for the right pointer. Setting -Duser.timezone=UTC has solved
the problem. Now, we don't see any more queries related to *SET TimeZone.*
Thanks again for your time and valuable suggestion.
@Jeff : These queries were sent by the JDBC Driver latest changes, nothing
to do w
On Fri, Oct 11, 2019 at 7:49 AM Amarendra Konda
wrote:
> Hi,
>
> In our test environment, it was observed that there are too many queries
> were getting fired to the database server,
>
What does "too many" mean here? Is it just more than you like to see in
your log file, or is there some object
On 10/13/19 10:24 PM, Amarendra Konda wrote:
Hi Adrian,
Thanks a lot for the response.
We are using JDBC Driver 42.2.8 along with the Tomcat Server on Java 8.
As part of application code, We are *_not_* setting timezone (or)
application names. One observation was, application was querying col
Hi Adrian,
Thanks a lot for the response.
We are using JDBC Driver 42.2.8 along with the Tomcat Server on Java 8. As
part of application code, We are *not* setting timezone (or) application
names. One observation was, application was querying columns of the
datatype "timestamp without time zone"
On 10/11/19 4:49 AM, Amarendra Konda wrote:
Hi,
In our test environment, it was observed that there are too many queries
were getting fired to the database server, even though they are not part
of the SQL query execution.
And the number of queries that were coming to server are very high. Ca
