Too many SET TimeZone and Application_name queries - Mailing list pgsql-general

From Amarendra Konda
Subject Too many SET TimeZone and Application_name queries
Date
Msg-id CAJNAD0=HYZ3KNmuA9aJvRWz=05MwsHs5g_Vbo8nBu=q1Nf0FnQ@mail.gmail.com
Whole thread Raw
Responses Re: Too many SET TimeZone and Application_name queries
Re: Too many SET TimeZone and Application_name queries
List pgsql-general
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 ?


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 






pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: JSON vs. JSONB storage size
Next
From: Charles Clavadetscher
Date:
Subject: Re: Trigger