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. Can > you please suggest on how to avoid these queries to the database server ?
My guess is your application server/framework is setting the below. What are you using for above?
> > > 2019-10-10 13:37:25 UTC:172.31.77.194(36920): > user1@new_unity_green1:[2549]:LOG: duration: 0.081 ms statement: *SET > application_name='PostgreSQL JDBC Driver';* > 2019-10-10 13:37:25 UTC:172.31.69.112(45682): > user1@new_unity_green0:[3545]:LOG: duration: 0.036 ms statement: *SET > TimeZone='UTC';* > 2019-10-10 13:37:25 > UTC:172.31.77.194(36902):user1@new_unity_green1:[2112]:LOG: duration: > 0.177 ms statement: *SET TimeZone='Etc/UTC';SET > application_name='PostgreSQL JDBC Driver';* > > > *_Environment_* > > * PGBouncer 1.9 > * JDBC Driver 42.2.8 > * Java 1.8 > * PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.3 > 20140911 (Red Hat 4.8.3-9), 64-bit > > > Application Server, pgBouncer and database server are all configured > with UTC only. > > =>show timezone; > TimeZone > ---------- > UTC > > Thanks in advance, > > Regards, Amarendra > > > > > >